Hi Cameleers, I'll just enumerate issues that I've found, please check on your end, update release procedures and backfill where necessary: - not creating releases on reporter.apache.org. I've added last releases, this needs to be done for older and future releases https://reporter.apache.org/addrelease.html?camel - not uploading release to dist.apache.org, sources are mandatory, binaries are optional - uploading sha1/md5 instead of sha512 hashes - not signing releases, and not adding the release manager's keys to KEYS file - not grouping issues for a release, practice varies, especially for GitHub driven sub-projects, we need to allow users to see what issues are fixed in what release, maintaining a change log is good, but it's not parsable and thus of no use on the website (or any other similar use case) - (wish) common naming of things: branch names, tag names, release artifacts - (wish) common usage of issue milestones, with common naming, labeling, etc.
Remember, we are bound by the policy of ASF, there is no option for doing things differently, if you wish to do things differently you need to engage with ASF and push through your changes. Documentation references: - https://www.apache.org/legal/release-policy.html - https://infra.apache.org/release-publishing.html - https://infra.apache.org/release-distribution.html zoran On Tue, Dec 1, 2020 at 1:59 PM Andrea Cosentino <anco...@gmail.com> wrote: > > The Camel Parent POM and release process has been more established and has > been more worked and reworked along the way. > > I do believe that the Apache releasing model is quite old and sometimes > take care of both the aspect of releasing (releasing and releasing the > Apache way) is quite an effort. > > I think it should be modernized at some point. > > Just my 2 cents. > > I'll follow up with the release managers about these. > > Il giorno mar 1 dic 2020 alle ore 13:41 Zoran Regvart <zo...@regvart.com> > ha scritto: > > > Hi Cameleers, > > I've been trying to rework the download and releases pages, to have > > LTS/latest/legacy and sub project releases and I've found several > > issues that I think need to be addressed by the release managers. > > > > I've created several JIRAs and assigned them to managers of particular > > releases, please do go through them and try to fix these issues. > > > > The inconsistency by which sub projects tend to diverge from what we > > have established as the norm in the main Camel release is quite > > disturbing. There are no two common ways of providing release > > binaries, naming released packages, naming the release tags, nor > > grouping issues of a release. > > > > This is deeply concerning to me and I do wish that folk more involved > > with each subproject took better care of managing this. > > > > zoran > > -- > > Zoran Regvart > > -- Zoran Regvart
