You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Nicolas Peltier <np...@apache.org> on 2021/01/14 21:47:01 UTC
[VOTE] Release Apache Sling Pipes 4.1.0
Hi,
We solved 7 issues in this release:
https://issues.apache.org/jira/projects/SLING/versions/12349395
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2398/
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 2398 /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,
RE: ***UNCHECKED*** Re: [VOTE] Release Apache Sling Pipes 4.1.0
Posted by Stefan Seifert <St...@diva-e.com.INVALID>.
can you add your key to https://people.apache.org/keys/group/sling.asc
see [1], appendix A
stefan
[1] https://sling.apache.org/documentation/development/release-management.html
>-----Original Message-----
>From: Nicolas Peltier <pe...@gmail.com>
>Sent: Friday, January 15, 2021 11:41 AM
>To: Sling Developers List <de...@sling.apache.org>
>Subject: ***UNCHECKED*** Re: [VOTE] Release Apache Sling Pipes 4.1.0
>
>Hey,
>
>spent quite some time yesterday to trying to send my new key to different
>key servers, thought as i could finally close the release in artifactory
>that it was good.
>attached it
>
>Le ven. 15 janv. 2021 à 00:04, Andreas Schaefer
><ma...@me.com.invalid> a écrit :
>+1 (non-binding)
>
>- Andy
>
>P.S.: the check does report gpg as bad because I do not have your
>(mailto:npeltier@apache.org) GPG key. Do you have one and if where can it
>be found?
>
>> On Jan 14, 2021, at 1:47 PM, Nicolas Peltier <ma...@apache.org>
>wrote:
>>
>> Hi,
>>
>> We solved 7 issues in this release:
>> https://issues.apache.org/jira/projects/SLING/versions/12349395
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachesling-2398/
>>
>> 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 2398 /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,
***UNCHECKED*** Re: [VOTE] Release Apache Sling Pipes 4.1.0
Posted by Nicolas Peltier <pe...@gmail.com>.
Hey,
spent quite some time yesterday to trying to send my new key to different
key servers, thought as i could finally close the release in artifactory
that it was good.
attached it
Le ven. 15 janv. 2021 à 00:04, Andreas Schaefer <sc...@me.com.invalid>
a écrit :
> +1 (non-binding)
>
> - Andy
>
> P.S.: the check does report gpg as bad because I do not have your (
> npeltier@apache.org) GPG key. Do you have one and if where can it be
> found?
>
> > On Jan 14, 2021, at 1:47 PM, Nicolas Peltier <np...@apache.org>
> wrote:
> >
> > Hi,
> >
> > We solved 7 issues in this release:
> > https://issues.apache.org/jira/projects/SLING/versions/12349395
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-2398/
> >
> > 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 2398 /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,
>
>
Re: [VOTE] Release Apache Sling Pipes 4.1.0
Posted by Andreas Schaefer <sc...@me.com.INVALID>.
+1 (non-binding)
- Andy
P.S.: the check does report gpg as bad because I do not have your (npeltier@apache.org) GPG key. Do you have one and if where can it be found?
> On Jan 14, 2021, at 1:47 PM, Nicolas Peltier <np...@apache.org> wrote:
>
> Hi,
>
> We solved 7 issues in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12349395
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-2398/
>
> 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 2398 /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,
Re: [VOTE] Release Apache Sling Pipes 4.1.0
Posted by Robert Munteanu <ro...@apache.org>.
On Thu, 2021-01-14 at 22:47 +0100, Nicolas Peltier wrote:
> Please vote to approve this release:
+1
Robert
Re: [VOTE] Release Apache Sling Pipes 4.1.0
Posted by da...@apache.org.
+1
David
On Thu, 14 Jan 2021 at 21:47, Nicolas Peltier <np...@apache.org> wrote:
> Hi,
>
> We solved 7 issues in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12349395
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-2398/
>
> 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 2398 /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,
>
[CANCEL][VOTE] Release Apache Sling Pipes 4.1.0
Posted by Nicolas Peltier <pe...@gmail.com>.
will redo a new release once below bug is fixed, and my key problem is
fixed too
Le ven. 15 janv. 2021 à 12:11, Nicolas Peltier <pe...@gmail.com>
a écrit :
> ho! ok, will cancel that release then, thanks for spotting this, Stefan
>
> Le ven. 15 janv. 2021 à 12:05, Stefan Seifert
> <St...@diva-e.com.invalid> a écrit :
>
>> i've a problem running the unit tests on windows. surefire output see
>> below.
>> i assume there is a problem with line endings, can you fix the test that
>> it is agnostic of unix/windows line endings?
>>
>> stefan
>>
>>
>> -------------------------------------------------------------------------------
>> Test set: org.apache.sling.pipes.internal.CommandExecutorImplTest
>>
>> -------------------------------------------------------------------------------
>> Tests run: 17, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4.657 s
>> <<< FAILURE! - in org.apache.sling.pipes.internal.CommandExecutorImplTest
>> org.apache.sling.pipes.internal.CommandExecutorImplTest.testFileCommandServlet
>> Time elapsed: 0.39 s <<< FAILURE!
>> org.junit.ComparisonFailure:
>> expected:<...:content"],"size":5}[]
>> > but was:<...:content"],"size":5}[
>> ]
>> >
>> at
>> org.apache.sling.pipes.internal.CommandExecutorImplTest.testFileCommandServlet(CommandExecutorImplTest.java:236)
>>
>> org.apache.sling.pipes.internal.CommandExecutorImplTest.testSimpleCommandServlet
>> Time elapsed: 0.265 s <<< FAILURE!
>> org.junit.ComparisonFailure:
>> expected:<...tent/foo"],"size":1}[]
>> > but was:<...tent/foo"],"size":1}[
>> ]
>> >
>> at
>> org.apache.sling.pipes.internal.CommandExecutorImplTest.testSimpleCommandServlet(CommandExecutorImplTest.java:200)
>>
>> org.apache.sling.pipes.internal.CommandExecutorImplTest.testChainedCommand
>> Time elapsed: 0.263 s <<< FAILURE!
>> org.junit.ComparisonFailure:
>> expected:<...a/carrot"],"size":5}[]
>> > but was:<...a/carrot"],"size":5}[
>> ]
>> >
>> at
>> org.apache.sling.pipes.internal.CommandExecutorImplTest.testChainedCommand(CommandExecutorImplTest.java:225)
>>
>>
>>
>>
>> >-----Original Message-----
>> >From: Nicolas Peltier <np...@apache.org>
>> >Sent: Thursday, January 14, 2021 10:47 PM
>> >To: Sling Developers List <de...@sling.apache.org>
>> >Subject: [VOTE] Release Apache Sling Pipes 4.1.0
>> >
>> >Hi,
>> >
>> >We solved 7 issues in this release:
>> >https://issues.apache.org/jira/projects/SLING/versions/12349395
>> >
>> >Staging repository:
>> >https://repository.apache.org/content/repositories/orgapachesling-2398/
>> >
>> >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 2398 /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,
>>
>
Re: [VOTE] Release Apache Sling Pipes 4.1.0
Posted by Nicolas Peltier <pe...@gmail.com>.
ho! ok, will cancel that release then, thanks for spotting this, Stefan
Le ven. 15 janv. 2021 à 12:05, Stefan Seifert
<St...@diva-e.com.invalid> a écrit :
> i've a problem running the unit tests on windows. surefire output see
> below.
> i assume there is a problem with line endings, can you fix the test that
> it is agnostic of unix/windows line endings?
>
> stefan
>
>
> -------------------------------------------------------------------------------
> Test set: org.apache.sling.pipes.internal.CommandExecutorImplTest
>
> -------------------------------------------------------------------------------
> Tests run: 17, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4.657 s
> <<< FAILURE! - in org.apache.sling.pipes.internal.CommandExecutorImplTest
> org.apache.sling.pipes.internal.CommandExecutorImplTest.testFileCommandServlet
> Time elapsed: 0.39 s <<< FAILURE!
> org.junit.ComparisonFailure:
> expected:<...:content"],"size":5}[]
> > but was:<...:content"],"size":5}[
> ]
> >
> at
> org.apache.sling.pipes.internal.CommandExecutorImplTest.testFileCommandServlet(CommandExecutorImplTest.java:236)
>
> org.apache.sling.pipes.internal.CommandExecutorImplTest.testSimpleCommandServlet
> Time elapsed: 0.265 s <<< FAILURE!
> org.junit.ComparisonFailure:
> expected:<...tent/foo"],"size":1}[]
> > but was:<...tent/foo"],"size":1}[
> ]
> >
> at
> org.apache.sling.pipes.internal.CommandExecutorImplTest.testSimpleCommandServlet(CommandExecutorImplTest.java:200)
>
> org.apache.sling.pipes.internal.CommandExecutorImplTest.testChainedCommand
> Time elapsed: 0.263 s <<< FAILURE!
> org.junit.ComparisonFailure:
> expected:<...a/carrot"],"size":5}[]
> > but was:<...a/carrot"],"size":5}[
> ]
> >
> at
> org.apache.sling.pipes.internal.CommandExecutorImplTest.testChainedCommand(CommandExecutorImplTest.java:225)
>
>
>
>
> >-----Original Message-----
> >From: Nicolas Peltier <np...@apache.org>
> >Sent: Thursday, January 14, 2021 10:47 PM
> >To: Sling Developers List <de...@sling.apache.org>
> >Subject: [VOTE] Release Apache Sling Pipes 4.1.0
> >
> >Hi,
> >
> >We solved 7 issues in this release:
> >https://issues.apache.org/jira/projects/SLING/versions/12349395
> >
> >Staging repository:
> >https://repository.apache.org/content/repositories/orgapachesling-2398/
> >
> >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 2398 /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,
>
RE: [VOTE] Release Apache Sling Pipes 4.1.0
Posted by Stefan Seifert <St...@diva-e.com.INVALID>.
i've a problem running the unit tests on windows. surefire output see below.
i assume there is a problem with line endings, can you fix the test that it is agnostic of unix/windows line endings?
stefan
-------------------------------------------------------------------------------
Test set: org.apache.sling.pipes.internal.CommandExecutorImplTest
-------------------------------------------------------------------------------
Tests run: 17, Failures: 3, Errors: 0, Skipped: 0, Time elapsed: 4.657 s <<< FAILURE! - in org.apache.sling.pipes.internal.CommandExecutorImplTest
org.apache.sling.pipes.internal.CommandExecutorImplTest.testFileCommandServlet Time elapsed: 0.39 s <<< FAILURE!
org.junit.ComparisonFailure:
expected:<...:content"],"size":5}[]
> but was:<...:content"],"size":5}[
]
>
at org.apache.sling.pipes.internal.CommandExecutorImplTest.testFileCommandServlet(CommandExecutorImplTest.java:236)
org.apache.sling.pipes.internal.CommandExecutorImplTest.testSimpleCommandServlet Time elapsed: 0.265 s <<< FAILURE!
org.junit.ComparisonFailure:
expected:<...tent/foo"],"size":1}[]
> but was:<...tent/foo"],"size":1}[
]
>
at org.apache.sling.pipes.internal.CommandExecutorImplTest.testSimpleCommandServlet(CommandExecutorImplTest.java:200)
org.apache.sling.pipes.internal.CommandExecutorImplTest.testChainedCommand Time elapsed: 0.263 s <<< FAILURE!
org.junit.ComparisonFailure:
expected:<...a/carrot"],"size":5}[]
> but was:<...a/carrot"],"size":5}[
]
>
at org.apache.sling.pipes.internal.CommandExecutorImplTest.testChainedCommand(CommandExecutorImplTest.java:225)
>-----Original Message-----
>From: Nicolas Peltier <np...@apache.org>
>Sent: Thursday, January 14, 2021 10:47 PM
>To: Sling Developers List <de...@sling.apache.org>
>Subject: [VOTE] Release Apache Sling Pipes 4.1.0
>
>Hi,
>
>We solved 7 issues in this release:
>https://issues.apache.org/jira/projects/SLING/versions/12349395
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-2398/
>
>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 2398 /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,