Hmm, so you mean we should primite not existing releases (for users and asf) as being actual partial releases? Not sure which sense it makes from my window when we have all we need to not create these ambiguitues. If release process is too heavy we can automate most of it already - we just never felt the need IIRC, but pushing artifacts manually saves burnings version numbers which always saves questions and bad time on consumer sides. Personally I always favor users to committers but we are free to make our lifes easier if it is not enough in your opinion, hope it makes sense to not think to us first.
Le lun. 31 oct. 2022 à 09:37, Michael Osipov <micha...@apache.org> a écrit : > Am 2022-10-31 um 08:45 schrieb Slawomir Jaranowski: > > Hi, > > > > We are talking about a situation which happens very rarely - canceling a > > vote. > > > > Adding the next manual step like post process tagging only for one reason > > is not justified. > > > > I think that when we have multiple release labels for issues and one will > > be released and second not, can be misunderstood for final users. > > Not every user follows the dev list and voting result. > > As said, the version will be closed as archived and you can even add a > note in JIRA. This should really do it. > In the past 10 years maybe 10 people asked why there is a tag in Git, > but nothing on Central. I linked the dev mailing list, done. > > Every single additional step will make it even worse. > > M > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
