I have submitted a new application to main F-Droid repository (via GitLab merge request) and got approved. But I found that half a day later, the application is still not searchable from main F-Droid repository’s web interface; though bot flagged my application build on the Wiki as success.
As I actually meant to use F-Droid as a primary channel for providing binaries, I would like to know more about the main F-Droid server/repository configuration (at f-droid.org), and what to expect in the term of response time:
After a new application metadata is added to fdroiddata GitLab repository, how long it usually takes to make a new application appear in main F-Droid repository and its web interface?
Does the process of adding new application (from newly-merged fdroiddata GitLab tree) to main F-Droid build server require manual intervention?
How often each application’s upstream is checked for update? For example, if a new version tag appeared on upstream VCS, how long the main F-Droid build server takes to notice the change?
Once upstream update is detected, how long it usually takes before the new version appear in main F-Droid repository and its web interface? And does this process require manual intervention/approval?
All of this assumes there are no toolchain, licensing, or policy compliance issue preventing the build from being made or distributed.
1. one or two days
2. once an app is added to fdroiddata.git, the rest of the process is automatic, at least in terms of new apps being added. There are some manually run steps there, but they are more or less transparent to the submitters.
3. the builds are run daily, unless there is a problem
4. about a day, it can be done manually or automatically based on git tags