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 12:14:53 UTC

[VOTE CANCEL] Release JCR Resource 3.0.12 and Resource Resolver 1.6.2

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 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
> >