In the best case, you should:
- tag your releases. This way, one always knows which commit to package for a specific release
- create and maintain an
export.cfg, with an icon, and version numbers raised at each release
Explanations why these things are useful for packagers, and how they are done, and done best, can be found below.
Either use github releases (for an how-to see here), or tag releases with your git client (github will automatically create a github release).
This is important so that packagers can find out which commit to package for a given release name.
Create an export.cfg file, with at least settings for android. Technically, f-droid (and android) requires
to have raising version codes with every release. But there are other things you should/could do:
- create and set an icon (package/icon)
- customize the unique name (package/unique_name), it should be according to java package naming conventions
- customize the app's name (package/name)
- set version name (version/name) and update it every release
- set version code (version/code) and update it every release
Those version code/version name updates need to be done in some commit between two releases.
Either do it manually in an editor, or, which is much easier, via the options part of the export->android menu in godot.