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/01/10 10:52:22 UTC
[VOTE] Release Apache Sling Resource Merger 1.3.6
Hi,
we fixed one issue in this release:
https://issues.apache.org/jira/browse/SLING-7366
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1845
You can use this UNIX script to download the release and verify the
signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
Usage:
sh check_staged_release.sh 1845 /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 Apache Sling Resource Merger 1.3.6
Posted by Daniel Klco <dk...@apache.org>.
+1
On Wed, Jan 10, 2018 at 4:03 AM, Robert Munteanu <ro...@apache.org> wrote:
> On Wed, 2018-01-10 at 11:52 +0100, Carsten Ziegeler wrote:
> > Please vote to approve this release:
>
> +1
>
> Robert
Re: [VOTE] Release Apache Sling Resource Merger 1.3.6
Posted by Robert Munteanu <ro...@apache.org>.
On Wed, 2018-01-10 at 11:52 +0100, Carsten Ziegeler wrote:
> Please vote to approve this release:
+1
Robert
Re: [VOTE] Release Apache Sling Resource Merger 1.3.6
Posted by Konrad Windszus <ko...@gmx.de>.
Actually 1.3.6 is worse, because it throws IOOBE (https://issues.apache.org/jira/browse/SLING-7375 <https://issues.apache.org/jira/browse/SLING-7375>) while 1.3.4 does not. That is much worse than having an incorrect order (like we had for some edge cases in 1.3.4)!
But I guess now it is too late. We should have 1.3.8 soon.
> On 15. Jan 2018, at 10:38, Carsten Ziegeler <cz...@apache.org> wrote:
>
> Because I pressed the button.... :(
>
> 1.3.6 is not worse than 1.3.4 (but not better either), 1.3.8 will
> hopefully fix the issue. Once I have confirmation I'll start the vote
> for that one.
>
> Carsten
>
>
> Oliver Lietz wrote
>> On Monday 15 January 2018 06:46:06 Carsten Ziegeler wrote:
>>> The vote passed with three binding +1 votes.
>>
>> Hi Carsten,
>>
>> why do we release when we have a known (critical) bug which is already fixed?
>>
>> Regards,
>> O.
>>
>>> Thanks
>>> Carsten
>>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
Re: [VOTE] Release Apache Sling Resource Merger 1.3.6
Posted by Carsten Ziegeler <cz...@apache.org>.
Because I pressed the button.... :(
1.3.6 is not worse than 1.3.4 (but not better either), 1.3.8 will
hopefully fix the issue. Once I have confirmation I'll start the vote
for that one.
Carsten
Oliver Lietz wrote
> On Monday 15 January 2018 06:46:06 Carsten Ziegeler wrote:
>> The vote passed with three binding +1 votes.
>
> Hi Carsten,
>
> why do we release when we have a known (critical) bug which is already fixed?
>
> Regards,
> O.
>
>> Thanks
>> Carsten
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
Re: [VOTE] Release Apache Sling Resource Merger 1.3.6
Posted by Oliver Lietz <ap...@oliverlietz.de>.
On Monday 15 January 2018 06:46:06 Carsten Ziegeler wrote:
> The vote passed with three binding +1 votes.
Hi Carsten,
why do we release when we have a known (critical) bug which is already fixed?
Regards,
O.
> Thanks
> Carsten
Re: [VOTE] Release Apache Sling Resource Merger 1.3.6
Posted by Carsten Ziegeler <cz...@apache.org>.
The vote passed with three binding +1 votes.
Thanks
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
Re: [VOTE] Release Apache Sling Resource Merger 1.3.6
Posted by Carsten Ziegeler <cz...@apache.org>.
+1
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org