release-management.md

Releases of Fly-Pie

Releases are published on Github. They are automatically created via Github Actions whenever a git tag is pushed. The progress of future releases is tracked with Github Milestones. Submitted issues will be assigned to a specific release (depending on their importance and complexity).

Version Numbers

GNOME Shell extensions should use integer numbers for their versioning. Therefore the version number of Fly-Pie will be increased by one whenever a new version is released.

Creating Releases

When a new version of Fly-Pie is released, the following steps are performed.

1. We base the following steps on the current main branch:

   git checkout main

2. First, the release date in the changelog.md needs to be updated. When this is done, the file has to be committed:

   git add docs/changelog.md
   git commit -m ":tada: Set release date"

3. Then, a tag is created and everything is pushed:

   git tag v<new version number>
   git push origin v<new version number>
   git push origin main

4. Finally, the version number of the metadata.json needs to be increased for the next release.

   git add metadata.json
   git commit -m ":tada: Bump version number"

5. Last but not least, the automatically created release needs to be renamed and an interesting description needs to be added.

6. Ultimately, the created [email protected] file is uploaded to https://extensions.gnome.org/. It will take some time to get reviewed there.

Changelog Index Continuous Integration