michael-o commented on PR #1035: URL: https://github.com/apache/maven/pull/1035#issuecomment-1455217572
> > > > > And this prevents release plugin as well (when doing a release from master)? > > > > > > > > > > > > this one would be a blocker to me > > > > > > > > > just saying nothing really prevents. create a branch `release/4.0.0-alpha` or `release/3.9.2` or `release/3.8.10` when starting the release process and then release from this branch. As is we do not block people merging to main branches during release process... Then once the release is done just create a PR from the `release/xxx` branch. The current way of releasing is a bit of legacy from svn days, > > > > > > Bah, even more work... > > says the one is asking people to create jira for everything :P actually it's just 2 command line: > > * git checkout -b release/.... > > * when done with the release from from the branch: `gh pr create -B` > > > I just find the "hey guys hold on your merge for a week or two I'm releasing so nobody touch anything" a bit archaic svn/cvs style :) But this was just a comment from the peanut gallery. And nothing prevent someone to do it at the end of day. > > BTW I'm not for ban direct push but not for this release reason. ...and how do you want to reconcile two diverging branches back to a linear history? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
