Opened 7 weeks ago
Last modified 2 weeks ago
#70606 new enhancement
Automatically publish base source releases to distfiles server
Reported by: | jmroot (Joshua Root) | Owned by: | admin@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | server/hosting | Version: | |
Keywords: | Cc: | ||
Port: |
Description
Similar to #70365, downloading the source tarball for selfupdate from GitHub is not always possible. Older systems currently have to use the rsync fallback, so we'll need to ensure that new releases become available via plain HTTP in a timely fashion before we can remove that fallback.
Change History (3)
comment:1 follow-up: 2 Changed 7 weeks ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 7 weeks ago by jmroot (Joshua Root)
Replying to ryandesign:
Yes I agree with mirroring these files automatically but I would like to mirror all of the release assets not just the source tarball.
That's fine of course. :)
comment:3 Changed 2 weeks ago by ryandesign (Ryan Carsten Schmidt)
I've put the 2.10.0 and 2.10.1 files on the distfiles server manually for now.
Note: See
TracTickets for help on using
tickets.
Yes I agree with mirroring these files automatically but I would like to mirror all of the release assets not just the source tarball.
For alpha/beta/rc releases the files should go in the testing folder.