Re: [VOTE] Release Maven Release version 3.0.0-M7

2022-10-31 Thread Michael Osipov
Am 2022-10-29 um 19:36 schrieb Michael Osipov: Hi, We solved 7 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317824=12351828 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/projects/MRELEASE/issues Staging repo:

Re: Clarify procedure for restarting releases

2022-10-31 Thread Romain Manni-Bucau
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

Re: Clarify procedure for restarting releases

2022-10-31 Thread Michael Osipov
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

Re: Clarify procedure for restarting releases

2022-10-31 Thread Guillaume Nodet
Le lun. 31 oct. 2022 à 08:46, Slawomir Jaranowski a écrit : > 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

Re: Clarify procedure for restarting releases

2022-10-31 Thread 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

Re: Clarify procedure for restarting releases

2022-10-31 Thread Romain Manni-Bucau
Le lun. 31 oct. 2022 à 07:34, Hervé Boutemy a écrit : > if pushing the tag is an additional manual step after the vote, experience > shows that it will be forgotten > Well it worked well for multiple projects so I'm sure it can work for maven. Dist is another deal and we can also invest

Re: Clarify procedure for restarting releases

2022-10-31 Thread Hervé Boutemy
if pushing the tag is an additional manual step after the vote, experience shows that it will be forgotten and even if we check its existence in dist-tool and publish what is missing, people will have to look at the report:

Re: Clarify procedure for restarting releases

2022-10-31 Thread Romain Manni-Bucau
+1 post-release tagging is the easiest (plus the fact a tag is a hash in git, not a name ;)) Le dim. 30 oct. 2022 à 21:40, Olivier Lamy a écrit : > +1 > > Exactly if the problem is the tag, we simply don’t push the tag. > m-release-p has options for that (don’t push and local clone). > The tag