Re: Proposal to add "release requirements" check

It's an interesting (but not practical) idea to base the set of active branches on the links in documentation pages.I would never try to do that really and it was never anywhere close to my proposal - scanning download pages is only to check if they have proper links/closer.lua script, nothing else

Re: Proposal to add "release requirements" check

On Mon, 8 Nov 2021 at 17:49, Jarek Potiuk wrote: > > > However this does not solve the issue of stale download pages: how do > you know when a release version is no longer supported? > > What do you mean? > > Is there a requirement for that that I missed? I believe the > requirement is only about

Re: Proposal to add "release requirements" check

I was also talking more from a user perspective. It's not that hard to create a one pager that contains the latest version, release dates, release notes and keys for all packages the project provides. In the case of Airflow it's pretty much what you put in announcements, and this one is fairly obv

Re: Proposal to add "release requirements" check

> On Nov 8, 2021, at 9:48 AM, Jarek Potiuk wrote: > >> However this does not solve the issue of stale download pages: how do > you know when a release version is no longer supported? > > What do you mean? > > Is there a requirement for that that I missed? I believe the > requirement is only

Re: Proposal to add "release requirements" check

> However this does not solve the issue of stale download pages: how do you know when a release version is no longer supported? What do you mean? Is there a requirement for that that I missed? I believe the requirement is only about removing artifacts from "downloads.a.o" and this is a completely

Re: Proposal to add "release requirements" check

On Mon, 8 Nov 2021 at 17:11, Jarek Potiuk wrote: > > Yeah. We will have different URLs especially as more artifacts are > produced (airflow has 3 of those each with different download pages). > > But this should be straightforward when you can add the url when > registering the release (as Sebb pr

Re: Proposal to add "release requirements" check

Yeah. We will have different URLs especially as more artifacts are produced (airflow has 3 of those each with different download pages). But this should be straightforward when you can add the url when registering the release (as Sebb proposed). According to the release process you should register

Re: Proposal to add "release requirements" check

On Mon, 8 Nov 2021 at 11:29, Hans Van Akelyen wrote: > > Hi, > > I think a certain level of uniformity would not be bad for this. > Having a fixed path to the downloads for each project makes it simpler for > the users to "shop" for Apache projects. > > Having .a.o/download/ as a link that should

Re: Proposal to add "release requirements" check

On Mon, 8 Nov 2021 at 11:19, Justin Mclean wrote: > > Hi, > > > However that assumes that you know where to find the download page(s). > > It also assumes that projects update their download page(s) to only > > show current releases. > > It does indeed assume that, and a few other things. Currentl

Re: Proposal to add "release requirements" check

Hi, I think a certain level of uniformity would not be bad for this. Having a fixed path to the downloads for each project makes it simpler for the users to "shop" for Apache projects. Having .a.o/download/ as a link that should point to the resources makes it simpler for everyone. Kind Regards,

Re: Proposal to add "release requirements" check

Hi, > However that assumes that you know where to find the download page(s). > It also assumes that projects update their download page(s) to only > show current releases. It does indeed assume that, and a few other things. Currently policy doesn't specify what the download page URL should be, b

Re: Proposal to add "release requirements" check

On Mon, 8 Nov 2021 at 00:49, Justin Mclean wrote: > > Hi, > > > Purging old releases needs at least two data sources: > > - the list of files on downloads.apache.org > > (or the dist.a.o source). > > This is trivial to obtain. > > - the list of current versions for