Hi, I've requested infra to add a feature to the closer.lua service as described in the attached email.
For example, the current JDO downloads page https://db.apache.org/jdo/downloads.html could include a brief description of the release and a simple link to https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.tar.gz and the linked page would have everything needed to download the release and verify the checksum and signatures. Regards, Craig > Begin forwarded message: > > From: Craig Russell <apache....@gmail.com> > Subject: Re: Extend closer.lua to act as a download page > Date: April 16, 2022 at 4:23:04 PM PDT > To: Greg Stein <gst...@gmail.com> > Cc: Users <us...@infra.apache.org>, JDO Project <jdo-...@db.apache.org>, > general@db.apache.org > > I'd like to ask on behalf of the DB PMC for the infra tool closer.lua to be > enhanced a bit for use by projects. > > It will be much easier for us if we can simply link to e.g. > https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.tar.gz > > <https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.tar.gz> > and have that page contain the .asc and .sha512 as well. > > Even better if closer.lua can also find the relevant KEYS file and link to it > when describing how to check the release. > > With this approach, it is easier for the project and less error-prone to > maintain the download page(s). We can include the current release as well as > archived releases on the same download page and omit the links to the .asc > and .sha512 and KEYS files. > > Please let us know how we can help. > > Regards, > Craig > > >> On Apr 16, 2022, at 2:01 AM, Greg Stein <gst...@gmail.com >> <mailto:gst...@gmail.com>> wrote: >> >> On Thu, Apr 14, 2022 at 4:43 PM sebb <seb...@gmail.com >> <mailto:seb...@gmail.com>> wrote: >> On Thu, 14 Apr 2022 at 20:52, Christopher <ctubb...@apache.org >> <mailto:ctubb...@apache.org>> wrote: >> > >> > Doing this would probably restrict INFRA's ability to adapt it to >> > their changing needs, as projects would become dependent on it. >> >> Projects are already dependent on the page. >> >> Correct. We *want* projects to use closer.lua. It provides a control point >> to direct users to the appropriate location to download. Today, it primarily >> sends them to our CDN and to an EU download location. >> >> Should those decisions ever change, we want projects to be using closer.lua >> to effect those changes. >> >> I think it would make it easier for Infra to make changes, as they >> would be able to adjust it. >> >> Yes. >> >> > Probably best to leave the mirror-management page independent from the >> > project download pages, since they serve the needs of separate groups. >> >> I was not suggesting replacing these, for those projects that want to >> customise the pages. >> >> Today, we no longer have a mirror system. But requiring projects to use >> closer.lua ensures that we can swap in that future option. >> >> All that said, as I recall: closer.lua provides support for .ezt pages so >> that projects can provide custom download pages. Maybe there is a way to >> provide the needed variables to projects' custom download page templates. >> >> Or, they can just keep using their pages. >> >> The download pages are owned by the TLPs. Infra isn't gonna interfere with >> them. Should any TLPs want more features, then they can ask. We haven't seen >> any requests in years from the TLPs. >> >> Cheers, >> Greg >> InfraAdmin, ASF >> > > Craig L Russell > c...@apache.org <mailto:c...@apache.org> > Craig L Russell c...@apache.org
