Re: [VOTE] Release Apache Sling Testing Clients 3.0.22

+1 On Mon, Jan 15, 2024 at 2:09 AM Andrei Dulvac wrote: > Hi, > > We solved 5 issues in this release: > https://issues.apache.org/jira/projects/SLING/versions/12353709 > > Staging repository: > https://repository.apache.org/content/repositories/orgapachesling-2829/ > > You can use this UNIX

Re: [PR] Various improvements for the webconsole plugin [sling-org-apache-sling-resourceresolver]

sonarcloud[bot] commented on PR #78: URL: https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/78#issuecomment-1896570829 ## [![Quality Gate Failed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/qg-failed-20px.png 'Quality

Re: [PR] SLING-11352 - Fix parsing of path-only mappings [sling-org-apache-sling-resourceresolver]

sonarcloud[bot] commented on PR #84: URL: https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/84#issuecomment-1896563047 ## [![Quality Gate Passed](https://sonarsource.github.io/sonarcloud-github-static-resources/v2/checks/QualityGateBadge/qg-passed-20px.png 'Quality

Re: [VOTE] Release Apache Resource Resolver 1.11.6

On 17.01.2024 13:44, Bertrand Delacretaz wrote: [X ] +1 Approve the release Julian's signature 44F4797A52C336FA666CD9271DE461528F1F1B2A was missing from https://downloads.apache.org/sling/KEYS , I have added it [1] from [0], it should appear in a few minutes. ::: Ups. Thanks. Best

Re: [VOTE] Release Apache Resource Resolver 1.11.6

On Wed, 2024-01-17 at 07:51 +0100, Julian Reschke wrote: > Please vote to approve this release: +1 Robert signature.asc Description: This is a digitally signed message part

Re: [VOTE] Release Apache Resource Resolver 1.11.6

[X ] +1 Approve the release Julian's signature 44F4797A52C336FA666CD9271DE461528F1F1B2A was missing from https://downloads.apache.org/sling/KEYS , I have added it [1] from [0], it should appear in a few minutes. -Bertrand [0] https://downloads.apache.org/jackrabbit/KEYS [1] FWIW, here's how

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

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

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

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

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

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