Re: Boost downloads and JFrog

From: Rainer Deyke (rdeyke_at_[hidden])
Date: 2024-01-09 08:16:24

On 08.01.24 14:09, Sam Darwin via Boost wrote:
> While GitHub Releases seems like the best plan, here are a few other
> details. JFrog is hosting:
> 1. development snapshots
> 2. beta and release-candidates
> 3. releases
> 
> The GitHub Releases paradigm is well designed for 3, and possibly 2.
> However it's not designed for "development snapshots" and would really be
> forcing that functionality.
> - Developers visit the GitHub releases page, and hopefully the top listing
> would be the latest actual release. If the main listing is a 'develop'
> snapshot and a 'master' snapshot, that could be confusing, since it isn't
> an official release.
> - A release is tied to a git tag.  While tags can be changed, they are
> usually expected to be immutable. Publishing a dev snapshot multiple times
> per day would constantly re-write the so-called 'snapshot' git tag.  Or
> fill up the page with 1000 releases. No.

Possible workaround: put the dev snapshots in a separate GitHub project 
that only exists to host development snapshots.  Let it fill up with 
thousands of releases.  If we hit some kind of GitHub limit, delete the 
whole project and start a new one.

-- 
Rainer Deyke (rainerd_at_[hidden])