User:F.trott/Release procedure for extensions
Using Lingo 1.2.0 as an example
- Ensure that the code reflects the new version, e.g. in comments, constants and extension credits
- extension.json
- release-notes.md
- Ensure that the last version is pushed to and merged on the server
- Go to the extensions directory, e.g.
cd Lingo
- Tag the extension with the new release id (using the specified gpg key for signature):
git tag -u foo@bar.com 1.2.0
- Tag the extension with
latest
(using the specified gpg key for signature):git tag --force -u foo@bar.com latest
- Push the tags:
git push gerrit --force --tags
- Update the extensions wiki page with new version number, release date, download links
- Update the version history if necessary
- Announce the new version