git to f-droid.org publish workflow
Since we're getting quite close to %Launch, its time to figure out a good publishing workflow to https://f-droid.org. I think we do not need to have this nailed down before launching, since it can be implemented after launch, and this is just for updating. Here's my proposal for how it could work:
- changes are submitted via merge requests
- when things are merged, they are available at the staging location: https://fdroid.gitlab.io/fdroid-website/
- once the staging location is ready, then the website release manager tags a "version code", e.g. an integer version value that is just incremented.
- when the "version code" git tag is verified, then the website is published to https://f-droid.org
For implementing # 4 there are two options I can think of:
- use an f-droid.org machine to run the whole jekyll process and publish to https://f-droid.org
- use gitlab-ci storing an SSH key there, and have it publish straight to https://f-droid.org