You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Matt Sicker <bo...@gmail.com> on 2018/01/20 17:42:21 UTC
[VOTE] Release Apache Chainsaw 2.0.0-rc2
This is a vote to release Apache Chainsaw 2.0.0-rc2
Source and binary artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
Committed under SVN revision 24337.
Site:
http://musigma.org/chainsaw-site/
https://github.com/jvz/chainsaw-site
Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc2 <
https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.git;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
>
Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D.
This vote will be open for at least 72 hours and requires at least 3 +1
votes and no more -1 votes than +1 votes.
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by Scott Deboy <sc...@gmail.com>.
Thanks Matt! Looks good!
Scott
On 1/25/18, Matt Sicker <bo...@gmail.com> wrote:
> This vote passes with 3 +1 votes from Scott Deboy, Remko Popma, and myself.
> I'll be following up with an announcement thread shortly.
>
> On 24 January 2018 at 18:50, Matt Sicker <bo...@gmail.com> wrote:
>
>> So far so good with this vote. I'll finish the release process tomorrow
>> morning (approximately 15 hours from the time of this email) if there are
>> no showstopper before then.
>>
>> On 22 January 2018 at 17:08, Remko Popma <re...@gmail.com> wrote:
>>
>>> +1
>>>
>>> (Shameless plug) Every java main() method deserves http://picocli.info
>>>
>>> > On Jan 23, 2018, at 7:29, Matt Sicker <bo...@gmail.com> wrote:
>>> >
>>> > I'll add my +1 from earlier. We still need another +1, though it's
>>> > only
>>> > been two days so far, so we still have time.
>>> >
>>> >> On 20 January 2018 at 16:54, Matt Sicker <bo...@gmail.com> wrote:
>>> >>
>>> >> I've committed the updated .asc files in revision 24339. MD5 and
>>> SHA-512
>>> >> hashes are still the same.
>>> >>
>>> >> Do note that you can also verify the git tag using the same gpg key
>>> >> via
>>> >> this command:
>>> >>
>>> >> git tag --verify chainsaw-2.0.0-rc2
>>> >>
>>> >>> On 20 January 2018 at 16:47, Matt Sicker <bo...@gmail.com> wrote:
>>> >>>
>>> >>> I didn't change my key (last 8 characters are the same as the short
>>> id).
>>> >>> Looks like I might have signed it wrong.
>>> >>>
>>> >>> On 20 January 2018 at 15:01, ralph.goers dslextreme.com <
>>> >>> ralph.goers@dslextreme.com> wrote:
>>> >>>
>>> >>>> Did you use a new signing key? When I try to verify I get
>>> >>>>
>>> >>>> gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc
>>> >>>> apache-chainsaw-2.0.0-bin.tar.gz
>>> >>>> gpg: Signature made Fri Nov 10 11:41:12 2017 MST
>>> >>>> gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C708
>>> >>>> 93B62BABE8
>>> >>>> gpg: BAD signature from "Matthew Sicker (Signing Key) <
>>> >>>> mattsicker@apache.org>" [undefined]
>>> >>>>
>>> >>>> Ralph
>>> >>>>
>>> >>>>
>>> >>>> ----- Original Message -----
>>> >>>> From: "Matt Sicker" <bo...@gmail.com>
>>> >>>> To: "Apache Logging Developers List" <de...@logging.apache.org>
>>> >>>> Sent: Saturday, January 20, 2018 10:42:21 AM
>>> >>>> Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2
>>> >>>>
>>> >>>> This is a vote to release Apache Chainsaw 2.0.0-rc2
>>> >>>>
>>> >>>> Source and binary artifacts:
>>> >>>>
>>> >>>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>>> >>>>
>>> >>>> Committed under SVN revision 24337.
>>> >>>>
>>> >>>> Site:
>>> >>>>
>>> >>>> http://musigma.org/chainsaw-site/
>>> >>>> https://github.com/jvz/chainsaw-site
>>> >>>>
>>> >>>> Git:
>>> >>>>
>>> >>>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>>> >>>> tag: chainsaw-2.0.0-rc2 <
>>> >>>> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.g
>>> >>>> it;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
>>> >>>>>
>>> >>>>
>>> >>>> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B
>>> 70FA1C814D.
>>> >>>>
>>> >>>> This vote will be open for at least 72 hours and requires at least
>>> >>>> 3
>>> +1
>>> >>>> votes and no more -1 votes than +1 votes.
>>> >>>>
>>> >>>> --
>>> >>>> Matt Sicker <bo...@gmail.com>
>>> >>>>
>>> >>>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Matt Sicker <bo...@gmail.com>
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> Matt Sicker <bo...@gmail.com>
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by Matt Sicker <bo...@gmail.com>.
This vote passes with 3 +1 votes from Scott Deboy, Remko Popma, and myself.
I'll be following up with an announcement thread shortly.
On 24 January 2018 at 18:50, Matt Sicker <bo...@gmail.com> wrote:
> So far so good with this vote. I'll finish the release process tomorrow
> morning (approximately 15 hours from the time of this email) if there are
> no showstopper before then.
>
> On 22 January 2018 at 17:08, Remko Popma <re...@gmail.com> wrote:
>
>> +1
>>
>> (Shameless plug) Every java main() method deserves http://picocli.info
>>
>> > On Jan 23, 2018, at 7:29, Matt Sicker <bo...@gmail.com> wrote:
>> >
>> > I'll add my +1 from earlier. We still need another +1, though it's only
>> > been two days so far, so we still have time.
>> >
>> >> On 20 January 2018 at 16:54, Matt Sicker <bo...@gmail.com> wrote:
>> >>
>> >> I've committed the updated .asc files in revision 24339. MD5 and
>> SHA-512
>> >> hashes are still the same.
>> >>
>> >> Do note that you can also verify the git tag using the same gpg key via
>> >> this command:
>> >>
>> >> git tag --verify chainsaw-2.0.0-rc2
>> >>
>> >>> On 20 January 2018 at 16:47, Matt Sicker <bo...@gmail.com> wrote:
>> >>>
>> >>> I didn't change my key (last 8 characters are the same as the short
>> id).
>> >>> Looks like I might have signed it wrong.
>> >>>
>> >>> On 20 January 2018 at 15:01, ralph.goers dslextreme.com <
>> >>> ralph.goers@dslextreme.com> wrote:
>> >>>
>> >>>> Did you use a new signing key? When I try to verify I get
>> >>>>
>> >>>> gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc
>> >>>> apache-chainsaw-2.0.0-bin.tar.gz
>> >>>> gpg: Signature made Fri Nov 10 11:41:12 2017 MST
>> >>>> gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C708
>> >>>> 93B62BABE8
>> >>>> gpg: BAD signature from "Matthew Sicker (Signing Key) <
>> >>>> mattsicker@apache.org>" [undefined]
>> >>>>
>> >>>> Ralph
>> >>>>
>> >>>>
>> >>>> ----- Original Message -----
>> >>>> From: "Matt Sicker" <bo...@gmail.com>
>> >>>> To: "Apache Logging Developers List" <de...@logging.apache.org>
>> >>>> Sent: Saturday, January 20, 2018 10:42:21 AM
>> >>>> Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2
>> >>>>
>> >>>> This is a vote to release Apache Chainsaw 2.0.0-rc2
>> >>>>
>> >>>> Source and binary artifacts:
>> >>>>
>> >>>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> >>>>
>> >>>> Committed under SVN revision 24337.
>> >>>>
>> >>>> Site:
>> >>>>
>> >>>> http://musigma.org/chainsaw-site/
>> >>>> https://github.com/jvz/chainsaw-site
>> >>>>
>> >>>> Git:
>> >>>>
>> >>>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>> >>>> tag: chainsaw-2.0.0-rc2 <
>> >>>> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.g
>> >>>> it;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
>> >>>>>
>> >>>>
>> >>>> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B
>> 70FA1C814D.
>> >>>>
>> >>>> This vote will be open for at least 72 hours and requires at least 3
>> +1
>> >>>> votes and no more -1 votes than +1 votes.
>> >>>>
>> >>>> --
>> >>>> Matt Sicker <bo...@gmail.com>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>> --
>> >>> Matt Sicker <bo...@gmail.com>
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Matt Sicker <bo...@gmail.com>
>> >>
>> >
>> >
>> >
>> > --
>> > Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by Matt Sicker <bo...@gmail.com>.
So far so good with this vote. I'll finish the release process tomorrow
morning (approximately 15 hours from the time of this email) if there are
no showstopper before then.
On 22 January 2018 at 17:08, Remko Popma <re...@gmail.com> wrote:
> +1
>
> (Shameless plug) Every java main() method deserves http://picocli.info
>
> > On Jan 23, 2018, at 7:29, Matt Sicker <bo...@gmail.com> wrote:
> >
> > I'll add my +1 from earlier. We still need another +1, though it's only
> > been two days so far, so we still have time.
> >
> >> On 20 January 2018 at 16:54, Matt Sicker <bo...@gmail.com> wrote:
> >>
> >> I've committed the updated .asc files in revision 24339. MD5 and SHA-512
> >> hashes are still the same.
> >>
> >> Do note that you can also verify the git tag using the same gpg key via
> >> this command:
> >>
> >> git tag --verify chainsaw-2.0.0-rc2
> >>
> >>> On 20 January 2018 at 16:47, Matt Sicker <bo...@gmail.com> wrote:
> >>>
> >>> I didn't change my key (last 8 characters are the same as the short
> id).
> >>> Looks like I might have signed it wrong.
> >>>
> >>> On 20 January 2018 at 15:01, ralph.goers dslextreme.com <
> >>> ralph.goers@dslextreme.com> wrote:
> >>>
> >>>> Did you use a new signing key? When I try to verify I get
> >>>>
> >>>> gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc
> >>>> apache-chainsaw-2.0.0-bin.tar.gz
> >>>> gpg: Signature made Fri Nov 10 11:41:12 2017 MST
> >>>> gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C708
> >>>> 93B62BABE8
> >>>> gpg: BAD signature from "Matthew Sicker (Signing Key) <
> >>>> mattsicker@apache.org>" [undefined]
> >>>>
> >>>> Ralph
> >>>>
> >>>>
> >>>> ----- Original Message -----
> >>>> From: "Matt Sicker" <bo...@gmail.com>
> >>>> To: "Apache Logging Developers List" <de...@logging.apache.org>
> >>>> Sent: Saturday, January 20, 2018 10:42:21 AM
> >>>> Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2
> >>>>
> >>>> This is a vote to release Apache Chainsaw 2.0.0-rc2
> >>>>
> >>>> Source and binary artifacts:
> >>>>
> >>>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
> >>>>
> >>>> Committed under SVN revision 24337.
> >>>>
> >>>> Site:
> >>>>
> >>>> http://musigma.org/chainsaw-site/
> >>>> https://github.com/jvz/chainsaw-site
> >>>>
> >>>> Git:
> >>>>
> >>>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
> >>>> tag: chainsaw-2.0.0-rc2 <
> >>>> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.g
> >>>> it;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
> >>>>>
> >>>>
> >>>> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B
> 70FA1C814D.
> >>>>
> >>>> This vote will be open for at least 72 hours and requires at least 3
> +1
> >>>> votes and no more -1 votes than +1 votes.
> >>>>
> >>>> --
> >>>> Matt Sicker <bo...@gmail.com>
> >>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Matt Sicker <bo...@gmail.com>
> >>>
> >>
> >>
> >>
> >> --
> >> Matt Sicker <bo...@gmail.com>
> >>
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by Remko Popma <re...@gmail.com>.
+1
(Shameless plug) Every java main() method deserves http://picocli.info
> On Jan 23, 2018, at 7:29, Matt Sicker <bo...@gmail.com> wrote:
>
> I'll add my +1 from earlier. We still need another +1, though it's only
> been two days so far, so we still have time.
>
>> On 20 January 2018 at 16:54, Matt Sicker <bo...@gmail.com> wrote:
>>
>> I've committed the updated .asc files in revision 24339. MD5 and SHA-512
>> hashes are still the same.
>>
>> Do note that you can also verify the git tag using the same gpg key via
>> this command:
>>
>> git tag --verify chainsaw-2.0.0-rc2
>>
>>> On 20 January 2018 at 16:47, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> I didn't change my key (last 8 characters are the same as the short id).
>>> Looks like I might have signed it wrong.
>>>
>>> On 20 January 2018 at 15:01, ralph.goers dslextreme.com <
>>> ralph.goers@dslextreme.com> wrote:
>>>
>>>> Did you use a new signing key? When I try to verify I get
>>>>
>>>> gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc
>>>> apache-chainsaw-2.0.0-bin.tar.gz
>>>> gpg: Signature made Fri Nov 10 11:41:12 2017 MST
>>>> gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C708
>>>> 93B62BABE8
>>>> gpg: BAD signature from "Matthew Sicker (Signing Key) <
>>>> mattsicker@apache.org>" [undefined]
>>>>
>>>> Ralph
>>>>
>>>>
>>>> ----- Original Message -----
>>>> From: "Matt Sicker" <bo...@gmail.com>
>>>> To: "Apache Logging Developers List" <de...@logging.apache.org>
>>>> Sent: Saturday, January 20, 2018 10:42:21 AM
>>>> Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2
>>>>
>>>> This is a vote to release Apache Chainsaw 2.0.0-rc2
>>>>
>>>> Source and binary artifacts:
>>>>
>>>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>>>>
>>>> Committed under SVN revision 24337.
>>>>
>>>> Site:
>>>>
>>>> http://musigma.org/chainsaw-site/
>>>> https://github.com/jvz/chainsaw-site
>>>>
>>>> Git:
>>>>
>>>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>>>> tag: chainsaw-2.0.0-rc2 <
>>>> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.g
>>>> it;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
>>>>>
>>>>
>>>> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D.
>>>>
>>>> This vote will be open for at least 72 hours and requires at least 3 +1
>>>> votes and no more -1 votes than +1 votes.
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>>
>>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by Matt Sicker <bo...@gmail.com>.
I'll add my +1 from earlier. We still need another +1, though it's only
been two days so far, so we still have time.
On 20 January 2018 at 16:54, Matt Sicker <bo...@gmail.com> wrote:
> I've committed the updated .asc files in revision 24339. MD5 and SHA-512
> hashes are still the same.
>
> Do note that you can also verify the git tag using the same gpg key via
> this command:
>
> git tag --verify chainsaw-2.0.0-rc2
>
> On 20 January 2018 at 16:47, Matt Sicker <bo...@gmail.com> wrote:
>
>> I didn't change my key (last 8 characters are the same as the short id).
>> Looks like I might have signed it wrong.
>>
>> On 20 January 2018 at 15:01, ralph.goers dslextreme.com <
>> ralph.goers@dslextreme.com> wrote:
>>
>>> Did you use a new signing key? When I try to verify I get
>>>
>>> gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc
>>> apache-chainsaw-2.0.0-bin.tar.gz
>>> gpg: Signature made Fri Nov 10 11:41:12 2017 MST
>>> gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C708
>>> 93B62BABE8
>>> gpg: BAD signature from "Matthew Sicker (Signing Key) <
>>> mattsicker@apache.org>" [undefined]
>>>
>>> Ralph
>>>
>>>
>>> ----- Original Message -----
>>> From: "Matt Sicker" <bo...@gmail.com>
>>> To: "Apache Logging Developers List" <de...@logging.apache.org>
>>> Sent: Saturday, January 20, 2018 10:42:21 AM
>>> Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2
>>>
>>> This is a vote to release Apache Chainsaw 2.0.0-rc2
>>>
>>> Source and binary artifacts:
>>>
>>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>>>
>>> Committed under SVN revision 24337.
>>>
>>> Site:
>>>
>>> http://musigma.org/chainsaw-site/
>>> https://github.com/jvz/chainsaw-site
>>>
>>> Git:
>>>
>>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>>> tag: chainsaw-2.0.0-rc2 <
>>> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.g
>>> it;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
>>> >
>>>
>>> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D.
>>>
>>> This vote will be open for at least 72 hours and requires at least 3 +1
>>> votes and no more -1 votes than +1 votes.
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by Matt Sicker <bo...@gmail.com>.
I've committed the updated .asc files in revision 24339. MD5 and SHA-512
hashes are still the same.
Do note that you can also verify the git tag using the same gpg key via
this command:
git tag --verify chainsaw-2.0.0-rc2
On 20 January 2018 at 16:47, Matt Sicker <bo...@gmail.com> wrote:
> I didn't change my key (last 8 characters are the same as the short id).
> Looks like I might have signed it wrong.
>
> On 20 January 2018 at 15:01, ralph.goers dslextreme.com <
> ralph.goers@dslextreme.com> wrote:
>
>> Did you use a new signing key? When I try to verify I get
>>
>> gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc
>> apache-chainsaw-2.0.0-bin.tar.gz
>> gpg: Signature made Fri Nov 10 11:41:12 2017 MST
>> gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C708
>> 93B62BABE8
>> gpg: BAD signature from "Matthew Sicker (Signing Key) <
>> mattsicker@apache.org>" [undefined]
>>
>> Ralph
>>
>>
>> ----- Original Message -----
>> From: "Matt Sicker" <bo...@gmail.com>
>> To: "Apache Logging Developers List" <de...@logging.apache.org>
>> Sent: Saturday, January 20, 2018 10:42:21 AM
>> Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2
>>
>> This is a vote to release Apache Chainsaw 2.0.0-rc2
>>
>> Source and binary artifacts:
>>
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>>
>> Committed under SVN revision 24337.
>>
>> Site:
>>
>> http://musigma.org/chainsaw-site/
>> https://github.com/jvz/chainsaw-site
>>
>> Git:
>>
>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>> tag: chainsaw-2.0.0-rc2 <
>> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.g
>> it;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
>> >
>>
>> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D.
>>
>> This vote will be open for at least 72 hours and requires at least 3 +1
>> votes and no more -1 votes than +1 votes.
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by Matt Sicker <bo...@gmail.com>.
I didn't change my key (last 8 characters are the same as the short id).
Looks like I might have signed it wrong.
On 20 January 2018 at 15:01, ralph.goers dslextreme.com <
ralph.goers@dslextreme.com> wrote:
> Did you use a new signing key? When I try to verify I get
>
> gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc
> apache-chainsaw-2.0.0-bin.tar.gz
> gpg: Signature made Fri Nov 10 11:41:12 2017 MST
> gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C70893B62BABE8
> gpg: BAD signature from "Matthew Sicker (Signing Key) <
> mattsicker@apache.org>" [undefined]
>
> Ralph
>
>
> ----- Original Message -----
> From: "Matt Sicker" <bo...@gmail.com>
> To: "Apache Logging Developers List" <de...@logging.apache.org>
> Sent: Saturday, January 20, 2018 10:42:21 AM
> Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2
>
> This is a vote to release Apache Chainsaw 2.0.0-rc2
>
> Source and binary artifacts:
>
> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>
> Committed under SVN revision 24337.
>
> Site:
>
> http://musigma.org/chainsaw-site/
> https://github.com/jvz/chainsaw-site
>
> Git:
>
> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
> tag: chainsaw-2.0.0-rc2 <
> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.git;a=tag;h=
> a9633a9bc4e7d635b893f7697e4a3dbae596795d
> >
>
> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D.
>
> This vote will be open for at least 72 hours and requires at least 3 +1
> votes and no more -1 votes than +1 votes.
>
> --
> Matt Sicker <bo...@gmail.com>
>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by "ralph.goers dslextreme.com" <ra...@dslextreme.com>.
Did you use a new signing key? When I try to verify I get
gpg --verify apache-chainsaw-2.0.0-bin.tar.gz.asc apache-chainsaw-2.0.0-bin.tar.gz
gpg: Signature made Fri Nov 10 11:41:12 2017 MST
gpg: using RSA key 9D0A56AAA0D60E0C0C7DCCC0B4C70893B62BABE8
gpg: BAD signature from "Matthew Sicker (Signing Key) <ma...@apache.org>" [undefined]
Ralph
----- Original Message -----
From: "Matt Sicker" <bo...@gmail.com>
To: "Apache Logging Developers List" <de...@logging.apache.org>
Sent: Saturday, January 20, 2018 10:42:21 AM
Subject: [VOTE] Release Apache Chainsaw 2.0.0-rc2
This is a vote to release Apache Chainsaw 2.0.0-rc2
Source and binary artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
Committed under SVN revision 24337.
Site:
http://musigma.org/chainsaw-site/
https://github.com/jvz/chainsaw-site
Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc2 <
https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.git;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
>
Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D.
This vote will be open for at least 72 hours and requires at least 3 +1
votes and no more -1 votes than +1 votes.
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Apache Chainsaw 2.0.0-rc2
Posted by Scott Deboy <sc...@gmail.com>.
+1
Pulled the git tag, built it and started Chainsaw from the standalone
tarball and zips.
Wandered through the website - there is cleanup to be done, but that's
work that can be done post-release.
Scott
On 1/20/18, Matt Sicker <bo...@gmail.com> wrote:
> This is a vote to release Apache Chainsaw 2.0.0-rc2
>
> Source and binary artifacts:
>
> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>
> Committed under SVN revision 24337.
>
> Site:
>
> http://musigma.org/chainsaw-site/
> https://github.com/jvz/chainsaw-site
>
> Git:
>
> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
> tag: chainsaw-2.0.0-rc2 <
> https://git-wip-us.apache.org/repos/asf?p=logging-chainsaw.git;a=tag;h=a9633a9bc4e7d635b893f7697e4a3dbae596795d
>>
>
> Artifacts signed by my key id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D.
>
> This vote will be open for at least 72 hours and requires at least 3 +1
> votes and no more -1 votes than +1 votes.
>
> --
> Matt Sicker <bo...@gmail.com>
>