Re: Order of steps in https://sling.apache.org/documentation/development/release-management.html

2024-01-17 Thread Konrad Windszus
Sounds good, can you make a proposal in a PR for https://github.com/apache/sling-site/blob/master/src/main/jbake/content/documentation/development/release-management.md? Thanks, Konrad > On 17. Jan 2024, at 11:36, Julian Reschke > wrote: > > On 17.01.2024 11:14, Carsten Ziegeler wrote: >> I

Re: Order of steps in https://sling.apache.org/documentation/development/release-management.html

2024-01-17 Thread Julian Reschke
On 17.01.2024 11:14, Carsten Ziegeler wrote: I think there is no perfect solution. We are operating this way for many years :) which of course doesn't mean there is no room for improvement. I think the scenario you describe happened at least once. but it was detected when the version was

Re: Order of steps in https://sling.apache.org/documentation/development/release-management.html

2024-01-17 Thread Konrad Windszus
I agree with Carsten here. I consider the outside view of JIRA being consistent more important here than to ease the work for committers in those hours while the release vote is ongoing (because every committer should be aware, at least theoretically). Konrad > On 17. Jan 2024, at 11:14,

Re: Order of steps in https://sling.apache.org/documentation/development/release-management.html

2024-01-17 Thread Carsten Ziegeler
I think there is no perfect solution. We are operating this way for many years :) which of course doesn't mean there is no room for improvement. I think the scenario you describe happened at least once. but it was detected when the version was released, the jira issue corrected and all was

Order of steps in https://sling.apache.org/documentation/development/release-management.html

2024-01-17 Thread Julian Reschke
Hi there, the "Release Management" document suggests adding a new (next) release should happen after the release vote, and that the release being voted on remains "unreleased" in the meantime. Doesn't that leave us with a time windos of 72h+ hours in which issue tracking in Jira will be