Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

This vote is cancelled and is superseded by the vote for 2.0.0-rc2.

On 20 January 2018 at 11:40, Scott Deboy  wrote:

> Sure
>
> On Jan 20, 2018 9:04 AM, "Matt Sicker"  wrote:
>
> > Wouldn't it be 2.0.0-rc2? Also, good timing: I can cut a new RC in the
> next
> > few hours.
> >
> > On 20 January 2018 at 09:47, Scott Deboy  wrote:
> >
> > > Matt, would you mind re-spinning a new build at 2.1.0-rc1?
> > >
> > > On 1/19/18, Scott Deboy  wrote:
> > > > I finally looked at this.  I pushed a change to app assembler config
> > > > to make the bin directory executable, and updated HOWTOBUILD to
> > > > mention you need to run mvn site:site first.
> > > >
> > > > Can we resin?
> > > >
> > > > On 11/13/17, Matt Sicker  wrote:
> > > >> Another thing I noticed is that the downloads page needs to be
> updated
> > > to
> > > >> link to the (future) dist URLs instead of ones in the site's
> directory
> > > >> (no
> > > >> proper mirroring in the old links).
> > > >>
> > > >> On 12 November 2017 at 19:25, Scott Deboy 
> > > wrote:
> > > >>
> > > >>> I don't recall why - it was a while back :)
> > > >>>
> > > >>> Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin
> > directory
> > > >>> issue.
> > > >>>
> > > >>> On 11/12/17, Matt Sicker  wrote:
> > > >>> > On 12 November 2017 at 13:53, Scott Deboy  >
> > > >>> > wrote:
> > > >>> >
> > > >>> >> That's right -forgot we rev'd to 2.1 internally (info.plist,
> > release
> > > >>> >> notes, couple other places).
> > > >>> >>
> > > >>> >
> > > >>> > Any particular reason?
> > > >>> >
> > > >>> >
> > > >>> >> Would it be easiest to release the new version as 2.1.0.0
> instead
> > of
> > > >>> >> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had
> an
> > > >>> >> official release with that rev.
> > > >>> >>
> > > >>> >
> > > >>> > I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since
> there's
> > > no
> > > >>> tags
> > > >>> > or releases for any 2.x release at all, so it seemed like a
> logical
> > > >>> > starting point.
> > > >>> >
> > > >>> > And thanks for testing! We should be able to clean up for a
> proper
> > > 2.x
> > > >>> > release. :)
> > > >>> >
> > > >>> > --
> > > >>> > Matt Sicker 
> > > >>> >
> > > >>>
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Matt Sicker 
> > > >>
> > > >
> > >
> >
> >
> >
> > --
> > Matt Sicker 
> >
>



-- 
Matt Sicker 

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

Sure

On Jan 20, 2018 9:04 AM, "Matt Sicker"  wrote:

> Wouldn't it be 2.0.0-rc2? Also, good timing: I can cut a new RC in the next
> few hours.
>
> On 20 January 2018 at 09:47, Scott Deboy  wrote:
>
> > Matt, would you mind re-spinning a new build at 2.1.0-rc1?
> >
> > On 1/19/18, Scott Deboy  wrote:
> > > I finally looked at this.  I pushed a change to app assembler config
> > > to make the bin directory executable, and updated HOWTOBUILD to
> > > mention you need to run mvn site:site first.
> > >
> > > Can we resin?
> > >
> > > On 11/13/17, Matt Sicker  wrote:
> > >> Another thing I noticed is that the downloads page needs to be updated
> > to
> > >> link to the (future) dist URLs instead of ones in the site's directory
> > >> (no
> > >> proper mirroring in the old links).
> > >>
> > >> On 12 November 2017 at 19:25, Scott Deboy 
> > wrote:
> > >>
> > >>> I don't recall why - it was a while back :)
> > >>>
> > >>> Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin
> directory
> > >>> issue.
> > >>>
> > >>> On 11/12/17, Matt Sicker  wrote:
> > >>> > On 12 November 2017 at 13:53, Scott Deboy 
> > >>> > wrote:
> > >>> >
> > >>> >> That's right -forgot we rev'd to 2.1 internally (info.plist,
> release
> > >>> >> notes, couple other places).
> > >>> >>
> > >>> >
> > >>> > Any particular reason?
> > >>> >
> > >>> >
> > >>> >> Would it be easiest to release the new version as 2.1.0.0 instead
> of
> > >>> >> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
> > >>> >> official release with that rev.
> > >>> >>
> > >>> >
> > >>> > I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's
> > no
> > >>> tags
> > >>> > or releases for any 2.x release at all, so it seemed like a logical
> > >>> > starting point.
> > >>> >
> > >>> > And thanks for testing! We should be able to clean up for a proper
> > 2.x
> > >>> > release. :)
> > >>> >
> > >>> > --
> > >>> > Matt Sicker 
> > >>> >
> > >>>
> > >>
> > >>
> > >>
> > >> --
> > >> Matt Sicker 
> > >>
> > >
> >
>
>
>
> --
> Matt Sicker 
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

Wouldn't it be 2.0.0-rc2? Also, good timing: I can cut a new RC in the next
few hours.

On 20 January 2018 at 09:47, Scott Deboy  wrote:

> Matt, would you mind re-spinning a new build at 2.1.0-rc1?
>
> On 1/19/18, Scott Deboy  wrote:
> > I finally looked at this.  I pushed a change to app assembler config
> > to make the bin directory executable, and updated HOWTOBUILD to
> > mention you need to run mvn site:site first.
> >
> > Can we resin?
> >
> > On 11/13/17, Matt Sicker  wrote:
> >> Another thing I noticed is that the downloads page needs to be updated
> to
> >> link to the (future) dist URLs instead of ones in the site's directory
> >> (no
> >> proper mirroring in the old links).
> >>
> >> On 12 November 2017 at 19:25, Scott Deboy 
> wrote:
> >>
> >>> I don't recall why - it was a while back :)
> >>>
> >>> Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory
> >>> issue.
> >>>
> >>> On 11/12/17, Matt Sicker  wrote:
> >>> > On 12 November 2017 at 13:53, Scott Deboy 
> >>> > wrote:
> >>> >
> >>> >> That's right -forgot we rev'd to 2.1 internally (info.plist, release
> >>> >> notes, couple other places).
> >>> >>
> >>> >
> >>> > Any particular reason?
> >>> >
> >>> >
> >>> >> Would it be easiest to release the new version as 2.1.0.0 instead of
> >>> >> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
> >>> >> official release with that rev.
> >>> >>
> >>> >
> >>> > I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's
> no
> >>> tags
> >>> > or releases for any 2.x release at all, so it seemed like a logical
> >>> > starting point.
> >>> >
> >>> > And thanks for testing! We should be able to clean up for a proper
> 2.x
> >>> > release. :)
> >>> >
> >>> > --
> >>> > Matt Sicker 
> >>> >
> >>>
> >>
> >>
> >>
> >> --
> >> Matt Sicker 
> >>
> >
>



-- 
Matt Sicker 

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

Matt, would you mind re-spinning a new build at 2.1.0-rc1?

On 1/19/18, Scott Deboy  wrote:
> I finally looked at this.  I pushed a change to app assembler config
> to make the bin directory executable, and updated HOWTOBUILD to
> mention you need to run mvn site:site first.
>
> Can we resin?
>
> On 11/13/17, Matt Sicker  wrote:
>> Another thing I noticed is that the downloads page needs to be updated to
>> link to the (future) dist URLs instead of ones in the site's directory
>> (no
>> proper mirroring in the old links).
>>
>> On 12 November 2017 at 19:25, Scott Deboy  wrote:
>>
>>> I don't recall why - it was a while back :)
>>>
>>> Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory
>>> issue.
>>>
>>> On 11/12/17, Matt Sicker  wrote:
>>> > On 12 November 2017 at 13:53, Scott Deboy 
>>> > wrote:
>>> >
>>> >> That's right -forgot we rev'd to 2.1 internally (info.plist, release
>>> >> notes, couple other places).
>>> >>
>>> >
>>> > Any particular reason?
>>> >
>>> >
>>> >> Would it be easiest to release the new version as 2.1.0.0 instead of
>>> >> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
>>> >> official release with that rev.
>>> >>
>>> >
>>> > I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's no
>>> tags
>>> > or releases for any 2.x release at all, so it seemed like a logical
>>> > starting point.
>>> >
>>> > And thanks for testing! We should be able to clean up for a proper 2.x
>>> > release. :)
>>> >
>>> > --
>>> > Matt Sicker 
>>> >
>>>
>>
>>
>>
>> --
>> Matt Sicker 
>>
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

I finally looked at this.  I pushed a change to app assembler config
to make the bin directory executable, and updated HOWTOBUILD to
mention you need to run mvn site:site first.

Can we resin?

On 11/13/17, Matt Sicker  wrote:
> Another thing I noticed is that the downloads page needs to be updated to
> link to the (future) dist URLs instead of ones in the site's directory (no
> proper mirroring in the old links).
>
> On 12 November 2017 at 19:25, Scott Deboy  wrote:
>
>> I don't recall why - it was a while back :)
>>
>> Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory
>> issue.
>>
>> On 11/12/17, Matt Sicker  wrote:
>> > On 12 November 2017 at 13:53, Scott Deboy 
>> > wrote:
>> >
>> >> That's right -forgot we rev'd to 2.1 internally (info.plist, release
>> >> notes, couple other places).
>> >>
>> >
>> > Any particular reason?
>> >
>> >
>> >> Would it be easiest to release the new version as 2.1.0.0 instead of
>> >> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
>> >> official release with that rev.
>> >>
>> >
>> > I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's no
>> tags
>> > or releases for any 2.x release at all, so it seemed like a logical
>> > starting point.
>> >
>> > And thanks for testing! We should be able to clean up for a proper 2.x
>> > release. :)
>> >
>> > --
>> > Matt Sicker 
>> >
>>
>
>
>
> --
> Matt Sicker 
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

Another thing I noticed is that the downloads page needs to be updated to
link to the (future) dist URLs instead of ones in the site's directory (no
proper mirroring in the old links).

On 12 November 2017 at 19:25, Scott Deboy  wrote:

> I don't recall why - it was a while back :)
>
> Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory
> issue.
>
> On 11/12/17, Matt Sicker  wrote:
> > On 12 November 2017 at 13:53, Scott Deboy  wrote:
> >
> >> That's right -forgot we rev'd to 2.1 internally (info.plist, release
> >> notes, couple other places).
> >>
> >
> > Any particular reason?
> >
> >
> >> Would it be easiest to release the new version as 2.1.0.0 instead of
> >> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
> >> official release with that rev.
> >>
> >
> > I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's no
> tags
> > or releases for any 2.x release at all, so it seemed like a logical
> > starting point.
> >
> > And thanks for testing! We should be able to clean up for a proper 2.x
> > release. :)
> >
> > --
> > Matt Sicker 
> >
>



-- 
Matt Sicker 

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

I don't recall why - it was a while back :)

Yes, I think 2.1.0-rc1 would make sense, once we fix the /bin directory issue.

On 11/12/17, Matt Sicker  wrote:
> On 12 November 2017 at 13:53, Scott Deboy  wrote:
>
>> That's right -forgot we rev'd to 2.1 internally (info.plist, release
>> notes, couple other places).
>>
>
> Any particular reason?
>
>
>> Would it be easiest to release the new version as 2.1.0.0 instead of
>> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
>> official release with that rev.
>>
>
> I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's no tags
> or releases for any 2.x release at all, so it seemed like a logical
> starting point.
>
> And thanks for testing! We should be able to clean up for a proper 2.x
> release. :)
>
> --
> Matt Sicker 
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

On 12 November 2017 at 13:53, Scott Deboy  wrote:

> That's right -forgot we rev'd to 2.1 internally (info.plist, release
> notes, couple other places).
>

Any particular reason?


> Would it be easiest to release the new version as 2.1.0.0 instead of
> 2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
> official release with that rev.
>

I could re-roll as 2.1.0-rc1 (or rc2?). I chose 2.0.0 since there's no tags
or releases for any 2.x release at all, so it seemed like a logical
starting point.

And thanks for testing! We should be able to clean up for a proper 2.x
release. :)

-- 
Matt Sicker 

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

When starting Chainsaw, I see this warning in the log:

menu 'Connect to' was NOT added because the 'Help' menu could not be located

There is a "Connect to" menu though, and the "Learn more about ZeroConf" 
works.



On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging KEYS
file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

That's right -forgot we rev'd to 2.1 internally (info.plist, release
notes, couple other places).

Would it be easiest to release the new version as 2.1.0.0 instead of
2.0.0-rc1?  Otherwise I could downgrade 2.1 refs, we never had an
official release with that rev.

Scott

On 11/12/17, Mikael Ståldal  wrote:
> In release notes in the app, it says version 2.1.
>
>
> On 2017-11-10 20:00, Matt Sicker wrote:
>> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>>
>> (Note: I've created release instructions on the new wiki: <
>> https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)
>>
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>>
>> Site:
>> http://musigma.org/chainsaw-site/
>>
>> Git:
>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>> tag: chainsaw-2.0.0-rc1
>>
>> All artifacts have been signed by my PGP key
>> id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging
>> KEYS
>> file.
>>
>> This vote will be open for at least 72 hours and requires at least 3 +1
>> votes and more +1 votes than -1 votes.
>>
>
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

I think we can either fix or remove that menu item from the menu after
the release - I don't know how useful it is.

Scott

On 11/12/17, Mikael Ståldal  wrote:
> When starting Chainsaw, I see this warning:
>
> Could not find any local JavaDocs, you might want to consider running
> 'ant javadoc'. The release version will be able to access Javadocs from
> the Apache website.
>
> And accessing Javadocs from the Help menu does not work.
>
>
>
> On 2017-11-10 20:00, Matt Sicker wrote:
>> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>>
>> (Note: I've created release instructions on the new wiki: <
>> https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)
>>
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>>
>> Site:
>> http://musigma.org/chainsaw-site/
>>
>> Git:
>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>> tag: chainsaw-2.0.0-rc1
>>
>> All artifacts have been signed by my PGP key
>> id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging
>> KEYS
>> file.
>>
>> This vote will be open for at least 72 hours and requires at least 3 +1
>> votes and more +1 votes than -1 votes.
>>
>
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

Would be nice to be able to load that as a plugin in a more dynamic 
fashion. But we can keep that for a future version, not blocking this 
release.



On 2017-11-12 20:45, Scott Deboy wrote:

That's right - we don't bundle in a JMS jar, although users can add
one to the classpath to use the JMSReceiver.

On 11/12/17, Mikael Ståldal  wrote:

When running Chainsaw, I see this error message:

Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks
like a dependent class is missing from the classpath
java.lang.NoClassDefFoundError: javax/jms/MessageListener

It seems to work anyway (without JMX support I suppose) though. But I
guess some jar file with that class should be on the classpath?


On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging
KEYS
file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

Fixed.

On 11/12/17, Mikael Ståldal  wrote:
> In the About text, it says:
>
> Please send questions, bug reports and/or feature requests to
> log4j-...@logging.apache.org
>
> which is obsolete.
>
>
> On 2017-11-10 20:00, Matt Sicker wrote:
>> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>>
>> (Note: I've created release instructions on the new wiki: <
>> https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)
>>
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>>
>> Site:
>> http://musigma.org/chainsaw-site/
>>
>> Git:
>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>> tag: chainsaw-2.0.0-rc1
>>
>> All artifacts have been signed by my PGP key
>> id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging
>> KEYS
>> file.
>>
>> This vote will be open for at least 72 hours and requires at least 3 +1
>> votes and more +1 votes than -1 votes.
>>
>
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

That's right - we don't bundle in a JMS jar, although users can add
one to the classpath to use the JMSReceiver.

On 11/12/17, Mikael Ståldal  wrote:
> When running Chainsaw, I see this error message:
>
> Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks
> like a dependent class is missing from the classpath
> java.lang.NoClassDefFoundError: javax/jms/MessageListener
>
> It seems to work anyway (without JMX support I suppose) though. But I
> guess some jar file with that class should be on the classpath?
>
>
> On 2017-11-10 20:00, Matt Sicker wrote:
>> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>>
>> (Note: I've created release instructions on the new wiki: <
>> https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)
>>
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>>
>> Site:
>> http://musigma.org/chainsaw-site/
>>
>> Git:
>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>> tag: chainsaw-2.0.0-rc1
>>
>> All artifacts have been signed by my PGP key
>> id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging
>> KEYS
>> file.
>>
>> This vote will be open for at least 72 hours and requires at least 3 +1
>> votes and more +1 votes than -1 votes.
>>
>
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

In release notes in the app, it says version 2.1.


On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging KEYS
file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

When starting Chainsaw, I see this warning:

Could not find any local JavaDocs, you might want to consider running 
'ant javadoc'. The release version will be able to access Javadocs from 
the Apache website.


And accessing Javadocs from the Help menu does not work.



On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging KEYS
file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

In the About text, it says:

Please send questions, bug reports and/or feature requests to
log4j-...@logging.apache.org

which is obsolete.


On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging KEYS
file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

When running Chainsaw, I see this error message:

Failed to locate Receiver class:org.apache.log4j.net.JMSReceiver, looks 
like a dependent class is missing from the classpath

java.lang.NoClassDefFoundError: javax/jms/MessageListener

It seems to work anyway (without JMX support I suppose) though. But I 
guess some jar file with that class should be on the classpath?



On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging KEYS
file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

The apache-chainsaw-2.0.0-standalone.tar.gz artifact has wrong 
permissions set on the bin directory:


$ tar -tvzf apache-chainsaw-2.0.0-standalone.tar.gz
d- 0/0 0 2017-11-10 19:24 apache-chainsaw/2.0.0/bin/

after extracting:

$ cd apache-chainsaw-2.0.0/
$ ls
bin  repo
$ cd bin/
bash: cd: bin/: Permission denied

I have to do:

$ chmod +rwx bin/
$ cd bin/
$ ls
chainsaw  chainsaw.bat

Same problem with apache-chainsaw-2.0.0-standalone.zip.

Most files and directories in both .tar.gz artifacts also has 
owner/group set to "matt/staff", which might not be appropriate.



On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging KEYS
file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

On 11 November 2017 at 14:44, Mikael Ståldal  wrote:

> On 2017-11-10 20:00, Matt Sicker wrote:
>
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>>
>
> When I look at that URL, it says: Revision 23059
>

I gave a specific revision so that, if necessary, you can check out that
exact revision, though there are no updates in the linked directory since
r23048. The revision number shown on that page is global to the whole dist
repo.

-- 
Matt Sicker 

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

Ah yes, I didn't note that correctly in the release wiki page. I've updated
the wiki.

On 11 November 2017 at 15:38, Mikael Ståldal  wrote:

> Yes, that worked.
>
>
>
> On 2017-11-11 22:22, Scott Deboy wrote:
>
>> I had ran mvn clean site:site install and it worked.
>>
>>
>> On 11/11/17, Mikael Ståldal  wrote:
>>
>>> On 2017-11-10 20:00, Matt Sicker wrote:
>>>
 Artifacts:
 https://dist.apache.org/repos/dist/dev/logging/chainsaw/
 svn revision 23048

>>>
>>> When I look at that URL, it says: Revision 23059
>>>
>>>
>>
>


-- 
Matt Sicker 

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

Yes, that worked.


On 2017-11-11 22:22, Scott Deboy wrote:

I had ran mvn clean site:site install and it worked.


On 11/11/17, Mikael Ståldal  wrote:

On 2017-11-10 20:00, Matt Sicker wrote:

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048


When I look at that URL, it says: Revision 23059

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

I had ran mvn clean site:site install and it worked.


On 11/11/17, Mikael Ståldal  wrote:
> On 2017-11-10 20:00, Matt Sicker wrote:
>> Artifacts:
>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>> svn revision 23048
>
> When I look at that URL, it says: Revision 23059
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

On 2017-11-10 20:00, Matt Sicker wrote:

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048


When I look at that URL, it says: Revision 23059

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

Same issue on master branch.

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-10T17:41:47+01:00)

Java version: 1.8.0_144, vendor: Oracle Corporation
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", arch: "amd64", family: "unix"


On 2017-11-11 21:40, Mikael Ståldal wrote:

$ git checkout chainsaw-2.0.0-rc1

$ mvn clean install

[...]

[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ 
apache-chainsaw ---
Downloading: 
https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar 

Downloaded: 
https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar 
(0 B at 0.0 KB/sec)

[INFO] Reading assembly descriptor: src/assembly/bin.xml
[INFO] 


[INFO] BUILD FAILURE
[INFO] 


[INFO] Total time: 17.828 s
[INFO] Finished at: 2017-11-11T21:31:50+01:00
[INFO] Final Memory: 31M/382M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.4:single 
(make-assembly) on project apache-chainsaw: site did not exist in the 
target directory - please run site:site before creating the assembly: 
Mojo configuration is invalid: site did not exist in the target 
directory - please run site:site before creating the assembly -> [Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException




On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>) 



Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging 
KEYS

file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Mikael Ståldal]

$ git checkout chainsaw-2.0.0-rc1

$ mvn clean install

[...]

[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ 
apache-chainsaw ---
Downloading: 
https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar
Downloaded: 
https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar 
(0 B at 0.0 KB/sec)

[INFO] Reading assembly descriptor: src/assembly/bin.xml
[INFO] 


[INFO] BUILD FAILURE
[INFO] 


[INFO] Total time: 17.828 s
[INFO] Finished at: 2017-11-11T21:31:50+01:00
[INFO] Final Memory: 31M/382M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:2.4:single 
(make-assembly) on project apache-chainsaw: site did not exist in the 
target directory - please run site:site before creating the assembly: 
Mojo configuration is invalid: site did not exist in the target 
directory - please run site:site before creating the assembly -> [Help 1]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the 
-e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException




On 2017-11-10 20:00, Matt Sicker wrote:

This is a vote to release Apache Chainsaw 2.0.0-rc1.

(Note: I've created release instructions on the new wiki: <
https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide>)

Artifacts:
https://dist.apache.org/repos/dist/dev/logging/chainsaw/
svn revision 23048

Site:
http://musigma.org/chainsaw-site/

Git:
https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
tag: chainsaw-2.0.0-rc1

All artifacts have been signed by my PGP key
id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging KEYS
file.

This vote will be open for at least 72 hours and requires at least 3 +1
votes and more +1 votes than -1 votes.

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

I can certainly update the screenshot for the site, though if it's embedded
in the bin archive, then that won't get updated. Thanks for verifying!

On 10 November 2017 at 14:43, Scott Deboy  wrote:

> Here's my +1.
>
> Site looks good, and it builds and runs.
>
> Thanks Matt
>
> On 11/10/17, Scott Deboy  wrote:
> > Updated screenshot.
> >
> > On 11/10/17, Scott Deboy  wrote:
> >> Awesome..I'll commit a new screenshot then.
> >>
> >> On 11/10/17, Ralph Goers  wrote:
> >>> The web site doesn’t have to be locked into the release.  An image can
> >>> be
> >>> updated after the release pretty easily.
> >>>
> >>> Ralph
> >>>
> >>>
>  On Nov 10, 2017, at 1:03 PM, Scott Deboy 
> wrote:
> 
>  Would it be possible for me to push an updated screenshot and re-spin?
> 
>  On 11/10/17, Scott Deboy  wrote:
> > Wow that screen shot looks ancient and ugly.  I should pull up
> > something on the Mac with updated default colors - it looks much
> > better.
> >
> > Scott
> >
> > On 11/10/17, Matt Sicker  wrote:
> >> Oh, and in case it isn't obvious how to test this, you can extract
> >> from
> >> either the zip or tar.gz files and run the chainsaw script in bin/
> >> corresponding to your operating system. Note that this crashes when
> >> using
> >> Java 9 for some reason, so make sure to use Java 6, 7, or 8.
> >>
> >> I built this using Java 1.8.0_111 on macOS 10.12.6.
> >>
> >> On 10 November 2017 at 13:04, Matt Sicker  wrote:
> >>
> >>> Quick note: using the maven-release-plugin doesn't seem to work in
> >>> this
> >>> project. Also, sources and documentation are included in the bin.*
> >>> files
> >>> while the standalone.* files are just the jars and startup scripts.
> >>>
> >>> On 10 November 2017 at 13:00, Matt Sicker 
> wrote:
> >>>
>  This is a vote to release Apache Chainsaw 2.0.0-rc1.
> 
>  (Note: I've created release instructions on the new wiki: <
>  https://cwiki.apache.org/confluence/display/LOGGING/Chainsa
>  w+Release+Guide>)
> 
>  Artifacts:
>  https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>  svn revision 23048
> 
>  Site:
>  http://musigma.org/chainsaw-site/
> 
>  Git:
>  https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>  tag: chainsaw-2.0.0-rc1
> 
>  All artifacts have been signed by my PGP key
>  id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the
>  Logging
>  KEYS file.
> 
>  This vote will be open for at least 72 hours and requires at least
>  3
>  +1
>  votes and more +1 votes than -1 votes.
> 
>  --
>  Matt Sicker 
> 
> >>>
> >>>
> >>>
> >>> --
> >>> Matt Sicker 
> >>>
> >>
> >>
> >>
> >> --
> >> Matt Sicker 
> >>
> >
> 
> >>>
> >>>
> >>>
> >>
> >
>



-- 
Matt Sicker 

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

Here's my +1.

Site looks good, and it builds and runs.

Thanks Matt

On 11/10/17, Scott Deboy  wrote:
> Updated screenshot.
>
> On 11/10/17, Scott Deboy  wrote:
>> Awesome..I'll commit a new screenshot then.
>>
>> On 11/10/17, Ralph Goers  wrote:
>>> The web site doesn’t have to be locked into the release.  An image can
>>> be
>>> updated after the release pretty easily.
>>>
>>> Ralph
>>>
>>>
 On Nov 10, 2017, at 1:03 PM, Scott Deboy  wrote:

 Would it be possible for me to push an updated screenshot and re-spin?

 On 11/10/17, Scott Deboy  wrote:
> Wow that screen shot looks ancient and ugly.  I should pull up
> something on the Mac with updated default colors - it looks much
> better.
>
> Scott
>
> On 11/10/17, Matt Sicker  wrote:
>> Oh, and in case it isn't obvious how to test this, you can extract
>> from
>> either the zip or tar.gz files and run the chainsaw script in bin/
>> corresponding to your operating system. Note that this crashes when
>> using
>> Java 9 for some reason, so make sure to use Java 6, 7, or 8.
>>
>> I built this using Java 1.8.0_111 on macOS 10.12.6.
>>
>> On 10 November 2017 at 13:04, Matt Sicker  wrote:
>>
>>> Quick note: using the maven-release-plugin doesn't seem to work in
>>> this
>>> project. Also, sources and documentation are included in the bin.*
>>> files
>>> while the standalone.* files are just the jars and startup scripts.
>>>
>>> On 10 November 2017 at 13:00, Matt Sicker  wrote:
>>>
 This is a vote to release Apache Chainsaw 2.0.0-rc1.

 (Note: I've created release instructions on the new wiki: <
 https://cwiki.apache.org/confluence/display/LOGGING/Chainsa
 w+Release+Guide>)

 Artifacts:
 https://dist.apache.org/repos/dist/dev/logging/chainsaw/
 svn revision 23048

 Site:
 http://musigma.org/chainsaw-site/

 Git:
 https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
 tag: chainsaw-2.0.0-rc1

 All artifacts have been signed by my PGP key
 id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the
 Logging
 KEYS file.

 This vote will be open for at least 72 hours and requires at least
 3
 +1
 votes and more +1 votes than -1 votes.

 --
 Matt Sicker 

>>>
>>>
>>>
>>> --
>>> Matt Sicker 
>>>
>>
>>
>>
>> --
>> Matt Sicker 
>>
>

>>>
>>>
>>>
>>
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

Updated screenshot.

On 11/10/17, Scott Deboy  wrote:
> Awesome..I'll commit a new screenshot then.
>
> On 11/10/17, Ralph Goers  wrote:
>> The web site doesn’t have to be locked into the release.  An image can be
>> updated after the release pretty easily.
>>
>> Ralph
>>
>>
>>> On Nov 10, 2017, at 1:03 PM, Scott Deboy  wrote:
>>>
>>> Would it be possible for me to push an updated screenshot and re-spin?
>>>
>>> On 11/10/17, Scott Deboy  wrote:
 Wow that screen shot looks ancient and ugly.  I should pull up
 something on the Mac with updated default colors - it looks much
 better.

 Scott

 On 11/10/17, Matt Sicker  wrote:
> Oh, and in case it isn't obvious how to test this, you can extract
> from
> either the zip or tar.gz files and run the chainsaw script in bin/
> corresponding to your operating system. Note that this crashes when
> using
> Java 9 for some reason, so make sure to use Java 6, 7, or 8.
>
> I built this using Java 1.8.0_111 on macOS 10.12.6.
>
> On 10 November 2017 at 13:04, Matt Sicker  wrote:
>
>> Quick note: using the maven-release-plugin doesn't seem to work in
>> this
>> project. Also, sources and documentation are included in the bin.*
>> files
>> while the standalone.* files are just the jars and startup scripts.
>>
>> On 10 November 2017 at 13:00, Matt Sicker  wrote:
>>
>>> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>>>
>>> (Note: I've created release instructions on the new wiki: <
>>> https://cwiki.apache.org/confluence/display/LOGGING/Chainsa
>>> w+Release+Guide>)
>>>
>>> Artifacts:
>>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>>> svn revision 23048
>>>
>>> Site:
>>> http://musigma.org/chainsaw-site/
>>>
>>> Git:
>>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>>> tag: chainsaw-2.0.0-rc1
>>>
>>> All artifacts have been signed by my PGP key
>>> id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the
>>> Logging
>>> KEYS file.
>>>
>>> This vote will be open for at least 72 hours and requires at least 3
>>> +1
>>> votes and more +1 votes than -1 votes.
>>>
>>> --
>>> Matt Sicker 
>>>
>>
>>
>>
>> --
>> Matt Sicker 
>>
>
>
>
> --
> Matt Sicker 
>

>>>
>>
>>
>>
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

Would it be possible for me to push an updated screenshot and re-spin?

On 11/10/17, Scott Deboy  wrote:
> Wow that screen shot looks ancient and ugly.  I should pull up
> something on the Mac with updated default colors - it looks much
> better.
>
> Scott
>
> On 11/10/17, Matt Sicker  wrote:
>> Oh, and in case it isn't obvious how to test this, you can extract from
>> either the zip or tar.gz files and run the chainsaw script in bin/
>> corresponding to your operating system. Note that this crashes when using
>> Java 9 for some reason, so make sure to use Java 6, 7, or 8.
>>
>> I built this using Java 1.8.0_111 on macOS 10.12.6.
>>
>> On 10 November 2017 at 13:04, Matt Sicker  wrote:
>>
>>> Quick note: using the maven-release-plugin doesn't seem to work in this
>>> project. Also, sources and documentation are included in the bin.* files
>>> while the standalone.* files are just the jars and startup scripts.
>>>
>>> On 10 November 2017 at 13:00, Matt Sicker  wrote:
>>>
 This is a vote to release Apache Chainsaw 2.0.0-rc1.

 (Note: I've created release instructions on the new wiki: <
 https://cwiki.apache.org/confluence/display/LOGGING/Chainsa
 w+Release+Guide>)

 Artifacts:
 https://dist.apache.org/repos/dist/dev/logging/chainsaw/
 svn revision 23048

 Site:
 http://musigma.org/chainsaw-site/

 Git:
 https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
 tag: chainsaw-2.0.0-rc1

 All artifacts have been signed by my PGP key
 id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging
 KEYS file.

 This vote will be open for at least 72 hours and requires at least 3 +1
 votes and more +1 votes than -1 votes.

 --
 Matt Sicker 

>>>
>>>
>>>
>>> --
>>> Matt Sicker 
>>>
>>
>>
>>
>> --
>> Matt Sicker 
>>
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Scott Deboy]

Wow that screen shot looks ancient and ugly.  I should pull up
something on the Mac with updated default colors - it looks much
better.

Scott

On 11/10/17, Matt Sicker  wrote:
> Oh, and in case it isn't obvious how to test this, you can extract from
> either the zip or tar.gz files and run the chainsaw script in bin/
> corresponding to your operating system. Note that this crashes when using
> Java 9 for some reason, so make sure to use Java 6, 7, or 8.
>
> I built this using Java 1.8.0_111 on macOS 10.12.6.
>
> On 10 November 2017 at 13:04, Matt Sicker  wrote:
>
>> Quick note: using the maven-release-plugin doesn't seem to work in this
>> project. Also, sources and documentation are included in the bin.* files
>> while the standalone.* files are just the jars and startup scripts.
>>
>> On 10 November 2017 at 13:00, Matt Sicker  wrote:
>>
>>> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>>>
>>> (Note: I've created release instructions on the new wiki: <
>>> https://cwiki.apache.org/confluence/display/LOGGING/Chainsa
>>> w+Release+Guide>)
>>>
>>> Artifacts:
>>> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
>>> svn revision 23048
>>>
>>> Site:
>>> http://musigma.org/chainsaw-site/
>>>
>>> Git:
>>> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
>>> tag: chainsaw-2.0.0-rc1
>>>
>>> All artifacts have been signed by my PGP key
>>> id 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging
>>> KEYS file.
>>>
>>> This vote will be open for at least 72 hours and requires at least 3 +1
>>> votes and more +1 votes than -1 votes.
>>>
>>> --
>>> Matt Sicker 
>>>
>>
>>
>>
>> --
>> Matt Sicker 
>>
>
>
>
> --
> Matt Sicker 
>

Re: [VOTE] Release Apache Chainsaw 2.0.0-rc1

[Matt Sicker]

Quick note: using the maven-release-plugin doesn't seem to work in this
project. Also, sources and documentation are included in the bin.* files
while the standalone.* files are just the jars and startup scripts.

On 10 November 2017 at 13:00, Matt Sicker  wrote:

> This is a vote to release Apache Chainsaw 2.0.0-rc1.
>
> (Note: I've created release instructions on the new wiki: <
> https://cwiki.apache.org/confluence/display/LOGGING/Chainsaw+Release+Guide
> >)
>
> Artifacts:
> https://dist.apache.org/repos/dist/dev/logging/chainsaw/
> svn revision 23048
>
> Site:
> http://musigma.org/chainsaw-site/
>
> Git:
> https://git-wip-us.apache.org/repos/asf/logging-chainsaw.git
> tag: chainsaw-2.0.0-rc1
>
> All artifacts have been signed by my PGP key id
> 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D as included in the Logging KEYS
> file.
>
> This vote will be open for at least 72 hours and requires at least 3 +1
> votes and more +1 votes than -1 votes.
>
> --
> Matt Sicker 
>



-- 
Matt Sicker