On 16/03/2022 17:53, sebb wrote:
As the subject says.
We currently use separate directories for binaries and source, each of
which may contain multiple versions.
This is a bit awkward to maintain compared with a directory per
release which would contain both binaries and source.
I think we should consider moving to individual release directories.
This would mean changes to various scripts etc, so would not be trivial.
If we do decide to do so, it would make sense to try this on a
component that normally only has one current version on release.
WDYT?
I like the idea in general. It makes managing releases a little easier.
However, there would be an impact is on users that have scripted
downloads. The change in the location will require changes to all of
those scripts. Does the benefit (primarily for us) justify the cost of
those changes (primarily for users)? This might be something to thing
about when we have a new major version.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
