You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Carsten Ziegeler <cz...@apache.org> on 2018/07/31 06:06:56 UTC
[VOTE] Release JCR Resource 3.0.12 and Resource Resolver 1.6.2
This release updates the two modules to the recently released API 2.18.2
We solved two issues in JCR Resource 3.0.12
https://issues.apache.org/jira/projects/SLING/versions/12343800
We solved two issues in Resource Resolver 1.6.2
https://issues.apache.org/jira/projects/SLING/versions/12343077
(There are still two open issues which are moved to 1.6.4, these issues
already existed in 1.6.0)
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1926/
You can use this UNIX script to download the release and verify the
signatures:
https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
Usage:
sh check_staged_release.sh 1926 /tmp/sling-staging
Please vote to approve this release:
[ ] +1 Approve the release
[ ] 0 Don't care
[ ] -1 Don't release, because ...
This majority vote is open for at least 72 hours.
Regards
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
Re: [VOTE CANCEL] Release JCR Resource 3.0.12 and Resource Resolver
1.6.2
Posted by Robert Munteanu <ro...@apache.org>.
Sure, reverted in c11a78e155e3eddc963423e199fbbd8566d6a9b7 .
Thanks,
Robert
On Tue, 2018-07-31 at 14:14 +0200, Carsten Ziegeler wrote:
> Thanks Robert,
>
> I didn't realize this either - so let's cancel the vote.
>
> Could you please take care of reverting?
>
> Thanks
>
> Carsten
>
>
> Robert Munteanu wrote
> > Hi Carsten,
> >
> > On Tue, 2018-07-31 at 08:06 +0200, Carsten Ziegeler wrote:
> > > We solved two issues in Resource Resolver 1.6.2
> > > https://issues.apache.org/jira/projects/SLING/versions/12343077
> > > (There are still two open issues which are moved to 1.6.4, these
> > > issues
> > > already existed in 1.6.0)
> >
> > I realise I have overlooked
> > https://issues.apache.org/jira/browse/SLING-7544 , which introduces
> > "a
> > potential race when new aliases get added while the intialization
> > was
> > still running" . This did not exist in previous relelases.
> >
> > Unfortunately I failed to either:
> >
> > a) revert the commit
> > b) find the time to review/propose a solution for the race
> > condition
> >
> > But I'm not sure if we should go through with a release like this
> > or
> > revert the initial commit and then re-run the release.
> >
> > Sorry about the complications,
> >
> > Robert
> >
[VOTE CANCEL] Release JCR Resource 3.0.12 and Resource Resolver 1.6.2
Posted by Carsten Ziegeler <cz...@apache.org>.
Thanks Robert,
I didn't realize this either - so let's cancel the vote.
Could you please take care of reverting?
Thanks
Carsten
Robert Munteanu wrote
> Hi Carsten,
>
> On Tue, 2018-07-31 at 08:06 +0200, Carsten Ziegeler wrote:
>> We solved two issues in Resource Resolver 1.6.2
>> https://issues.apache.org/jira/projects/SLING/versions/12343077
>> (There are still two open issues which are moved to 1.6.4, these
>> issues
>> already existed in 1.6.0)
>
> I realise I have overlooked
> https://issues.apache.org/jira/browse/SLING-7544 , which introduces "a
> potential race when new aliases get added while the intialization was
> still running" . This did not exist in previous relelases.
>
> Unfortunately I failed to either:
>
> a) revert the commit
> b) find the time to review/propose a solution for the race condition
>
> But I'm not sure if we should go through with a release like this or
> revert the initial commit and then re-run the release.
>
> Sorry about the complications,
>
> Robert
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
Re: [VOTE] Release JCR Resource 3.0.12 and Resource Resolver 1.6.2
Posted by Robert Munteanu <ro...@apache.org>.
Hi Carsten,
On Tue, 2018-07-31 at 08:06 +0200, Carsten Ziegeler wrote:
> We solved two issues in Resource Resolver 1.6.2
> https://issues.apache.org/jira/projects/SLING/versions/12343077
> (There are still two open issues which are moved to 1.6.4, these
> issues
> already existed in 1.6.0)
I realise I have overlooked
https://issues.apache.org/jira/browse/SLING-7544 , which introduces "a
potential race when new aliases get added while the intialization was
still running" . This did not exist in previous relelases.
Unfortunately I failed to either:
a) revert the commit
b) find the time to review/propose a solution for the race condition
But I'm not sure if we should go through with a release like this or
revert the initial commit and then re-run the release.
Sorry about the complications,
Robert
Re: [VOTE] Release JCR Resource 3.0.12 and Resource Resolver 1.6.2
Posted by Carsten Ziegeler <cz...@apache.org>.
+1
Carsten Ziegeler wrote
> This release updates the two modules to the recently released API 2.18.2
>
> We solved two issues in JCR Resource 3.0.12
> https://issues.apache.org/jira/projects/SLING/versions/12343800
>
> We solved two issues in Resource Resolver 1.6.2
> https://issues.apache.org/jira/projects/SLING/versions/12343077
> (There are still two open issues which are moved to 1.6.4, these issues
> already existed in 1.6.0)
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1926/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD
>
> Usage:
> sh check_staged_release.sh 1926 /tmp/sling-staging
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] 0 Don't care
> [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>
> Regards
> Carsten
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
RE: [VOTE] Release JCR Resource 3.0.12 and Resource Resolver 1.6.2
Posted by Stefan Seifert <ss...@pro-vision.de>.
+1