I already noticed this minor inconvenience in the past, but once a build is successful, the new release sometimes takes several days to become available for download in the repository. For example, this build succeeded the 19th in the morning, the batch finished in the evening, but the build still isn’t available for download. If I recall correctly, this build took almost two weeks between the upstream release and the build being actually available for download.
How long does it usually take for the update to appear in the store once the build is done? Is there some caching involved? Can we do something to speed up the process? As a more general thought, I’m wondering if the “daily batch” model isn’t reaching some scaling issues. You have to wait 1 or 2 days for the new upstream versions to get caught by “checkupdates”, if a batch is currently running wait for it to finish which can sometimes take several days, wait for a new batch to complete which can also take several days to get started and again several days to finish, and then wait an unknown amount of time for the app being actually available for download. Yet you could theoretically start the build as soon as metadata are pushed and publish the app in the process. Are there any ongoing discussions about this issue? I guess that’s hard to solve as it looks like a major paradigm change.