On Mon, 8 Nov 2021 at 11:29, Hans Van Akelyen <hans.van.akel...@gmail.com> 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 <project>.a.o/download/ as a link that should point to the resources > makes it simpler for everyone.
I agree, but expect a lot of complaints if you try to get this enforced. (and there's not much point unless it is enforced). > Kind Regards, > Hans > > On Mon, 8 Nov 2021 at 12:19, Justin Mclean <jus...@classsoftware.com> 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. Currently policy > > doesn't specify what the download page URL should be, but once known I > > would guess it wouldn’t change often. > > > > Kind Regards, > > Justin > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > For additional commands, e-mail: dev-h...@community.apache.org > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
