Re: Distribution location was: [VOTE] Release Apache Log4j 3.0.0-beta2 RC1
Hi Ralph, On Mon, 19 Feb 2024 at 05:03, Ralph Goers wrote: > > Just navigate to https://archive.apache.org/dist/logging/ and take a look. > Note that under log4j you will find version directories. Under log4j-audit > you will not find directories. Basically it is however they get added to > https://dist.apache.org/repos/dist/dev/logging/. It is just a mirror of what > gets committed there. Thanks for the explanation. I didn't notice that https://dist.apache.org/repos/dist/release/logging/ and https://dist.apache.org/repos/dist/dev/logging/ has a different directory structure: the former has directories like /log4j/2.22.1, the latter only /log4j. Therefore we probably just need to upload the RCs to `/dist/dev/logging/log4j/2.x` and `/dist/dev/logging/log4j/3.x`. The release manager will then move them to the appropriate folder in `/dist/release/logging/log4j`. Piotr
Re: Distribution location was: [VOTE] Release Apache Log4j 3.0.0-beta2 RC1
Just navigate to https://archive.apache.org/dist/logging/ and take a look. Note that under log4j you will find version directories. Under log4j-audit you will not find directories. Basically it is however they get added to https://dist.apache.org/repos/dist/dev/logging/. It is just a mirror of what gets committed there. I would suggest it makes sense to use version directories on a project that has lots of releases. For consistency it would make sense to do that everywhere but that ship has already sailed for existing projects. Ralph > On Feb 18, 2024, at 10:09 AM, Piotr P. Karwasz > wrote: > > Hi Gary, > > On Sun, 18 Feb 2024 at 15:12, Gary Gregory wrote: >> Note that the verification instructions below or the distro process or >> both need changes because the wget and all commands get EVERYTHING and >> work on EVERYTHING, which in this case means that BOTH release >> candidates for 2.23.0 and 3.0.0-beta2 are downloaded and instructions >> work on both at the same time, obviously not the intent. >> >> Over at Commons, we account for this use case by using the version in >> the distro folder, so, for example, here you'd RC in >> https://dist.apache.org/repos/dist/dev/logging/log4j/3.0.0-beta2, not >> https://dist.apache.org/repos/dist/dev/logging/log4j > > +1 for version specific folders. > > You didn't notice it but the CI removed the 2.23.0 distribution files, > when it committed 3.0.0-beta2. > > How exactly does `dist.apache.org` work with `archive.apache.org`? > Will it still work with directories like `/log4j/3.0.0-beta2/`? > > Piotr
Distribution location was: [VOTE] Release Apache Log4j 3.0.0-beta2 RC1
Hi Gary, On Sun, 18 Feb 2024 at 15:12, Gary Gregory wrote: > Note that the verification instructions below or the distro process or > both need changes because the wget and all commands get EVERYTHING and > work on EVERYTHING, which in this case means that BOTH release > candidates for 2.23.0 and 3.0.0-beta2 are downloaded and instructions > work on both at the same time, obviously not the intent. > > Over at Commons, we account for this use case by using the version in > the distro folder, so, for example, here you'd RC in > https://dist.apache.org/repos/dist/dev/logging/log4j/3.0.0-beta2, not > https://dist.apache.org/repos/dist/dev/logging/log4j +1 for version specific folders. You didn't notice it but the CI removed the 2.23.0 distribution files, when it committed 3.0.0-beta2. How exactly does `dist.apache.org` work with `archive.apache.org`? Will it still work with directories like `/log4j/3.0.0-beta2/`? Piotr