Aw: [DISCUSS] Commits report

[Benjamin Graf]

Hi Clebert,
 
this really gives a good overview what happened!
 
big +1
 
Regards
Benjamin
 

Gesendet: Donnerstag, 17. Mai 2018 um 04:52 Uhr
Von: "Clebert Suconic" 
An: dev@activemq.apache.org
Betreff: [DISCUSS] Commits report
Before someone asks on the VOTE Thread.. I wanted to point out that I
made a small project to parse git commit and generate a report.

I have ran the report on top of artemis and I'm adding a commit report
here that can be useful at least on the voter's thread:

https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0/artemis-2.6.0.html



I think it would be useful to have this one on top of the release
report as well. If nobody opposes I would like to add it to the next
release report.

The report generator current lives on my github page but it could be
moved somewhere else if someone bothers about being on my github fork:

https://github.com/clebertsuconic/git-release-report[https://github.com/clebertsuconic/git-release-report]

--
Clebert Suconic

Re: [DISCUSS] Commits report

[Francesco Nigro]

Nice!!!

Il giorno gio 17 mag 2018 alle ore 10:55 Benjamin Graf <
benjamin.g...@gmx.net> ha scritto:

> Hi Clebert,
>
> this really gives a good overview what happened!
>
> big +1
>
> Regards
> Benjamin
>
>
> Gesendet: Donnerstag, 17. Mai 2018 um 04:52 Uhr
> Von: "Clebert Suconic" 
> An: dev@activemq.apache.org
> Betreff: [DISCUSS] Commits report
> Before someone asks on the VOTE Thread.. I wanted to point out that I
> made a small project to parse git commit and generate a report.
>
> I have ran the report on top of artemis and I'm adding a commit report
> here that can be useful at least on the voter's thread:
>
>
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0/artemis-2.6.0.html
>
>
>
> I think it would be useful to have this one on top of the release
> report as well. If nobody opposes I would like to add it to the next
> release report.
>
> The report generator current lives on my github page but it could be
> moved somewhere else if someone bothers about being on my github fork:
>
>
> https://github.com/clebertsuconic/git-release-report[https://github.com/clebertsuconic/git-release-report]
>
> --
> Clebert Suconic
>

Re: [VOTE] Apache ActiveMQ Artemis 2.6.0

[Francesco Nigro]

+1 for me as well!

Il giorno gio 17 mag 2018 alle ore 07:01 Howard Gao 
ha scritto:

> +1
>
> On Thu, May 17, 2018 at 10:49 AM, Clebert Suconic <
> clebert.suco...@gmail.com
> > wrote:
>
> > I would like to propose an Apache ActiveMQ Artemis 2.6.0 release.
> >
> > The release notes can be found here:
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> > version=12342903&=12315920
> >
> > There is a new commits report I made that I'm introducing on this
> release:
> > https://dist.apache.org/repos/dist/dev/activemq/activemq-
> > artemis/2.6.0/artemis-2.6.0.html
> >
> > Source and binary distributions can be found here:
> > https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0
> >
> > The Maven repository is here:
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-1157
> >
> > In case you want to give it a try with the maven repo on examples:
> > http://activemq.apache.org/artemis/docs/latest/hacking-
> > guide/validating-releases.html
> >
> > The source tag:
> > https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.
> > git;a=tag;h=refs/tags/2.6.0
> >
> > I will update the website after the vote has passed.
> >
> >
> > [ ] +1 approve the release as Apache Artemis 2.4.0
> > [ ] +0 no opinion
> > [ ] -1 disapprove (and reason why)
> >
> >
> > Here's my +1
> >
>

Re: [HEADS-UP] 2.5.1 in one week

[Robbie Gemmell]

It was clear a release was coming at some point, however I think Tim's
mail is more around that it was actually not clear precisely when it
would, and so a notice would have been nice. If anything the mail
thread made it less clear when it would arrive, given it had been
coming for several weeks and the previous mail was 6 days before the
one saying you had tagged it.

I have no issue with lack of heads up mail in general, especially when
its well understood the point it will release (e.g JIRAs assigned
being resolved) or releases are frequent enough it simply becomes much
less important, but I also think it would have been good in this case
given the several prior heads ups served to somewhat mislead.

On 16 May 2018 at 17:32, Clebert Suconic  wrote:
> I have been pushing this for a few weeks.  I thought it was more than
> clear.  I didn’t mean to get anyone by surprise.
>
> Along the conversation here 2.5.1 will just be renamed as 2.6.0.
>
>
> I’m traveling today and I wanted to tag and upload from home.  And I wanted
> something to do tonight at the hotel :).  Sorry for any trouble.
>
> We can try another one shortly in a few weeks. (2 or 3)
>
> On Wed, May 16, 2018 at 11:53 AM Timothy Bish  wrote:
>
>> On 05/16/2018 11:09 AM, Clebert Suconic wrote:
>> > I just tagged as 2.6.0... It's uploading...
>> >
>> > I will cleanup JIRA tonight / tomorrow.. should send the voting thread
>> > soon (tonight or tomorrow)
>>
>> This seems a bit backwards to me.  I'd think in the future it'd be nice
>> to send some notice before you spin the release to give folks some
>> warning.  The title of this thread still references a 2.5.1 release in a
>> week which are both incorrect so anyone watching for it might miss the
>> notice and anyone working on last minute fixes or whatnot gets no notice.
>>
>> It'd probably be a good idea to do the JIRA cleanup prior to all this as
>> a way to better gauge where things stand before pulling the trigger and
>> also give people some better insight into what is in the release when
>> the vote thread appears.
>>
>> It probably wouldn't be as big a deal if releases were happening on a
>> more frequent basis but given the long delay I'd say some warning next
>> time would probably be the courteous thing to do.
>>
>> > On Thu, May 10, 2018 at 10:33 AM, Clebert Suconic
>> >  wrote:
>> >> I have been clearing the testsuite. Other guys are working with me on
>> >> that (Francesco, Justin for instance). I'll do as soon as I'm done.
>> >>
>> >> On Thu, May 10, 2018 at 8:24 AM, Christopher Shannon
>> >>  wrote:
>> >>> +1 to make this a 2.6.0 release, there are now over 80 commits and
>> >>> been enough time that I think a 2.6.0 makes more sense
>> >>>
>> >>> On Thu, May 3, 2018 at 12:09 PM, Clebert Suconic
>> >>>  wrote:
>>  Meanwhile please set your fixes as 2.5.1... i will rename it as 2.6.0
>>  before releasing as everything is already filtered there.
>> 
>>  On Thu, May 3, 2018 at 12:04 PM, Clebert Suconic
>>   wrote:
>> >  From the entire set.. we only have fixes.. and 4 enhancements...
>> > (previously existent features).
>> >
>> > I would prefer saving 2.6.0 for a more substantial release.. but if
>> > you guys still prefer calling 2.6.0 I'm fine with that.
>> >
>> > On Thu, May 3, 2018 at 11:02 AM, Robbie Gemmell
>> >  wrote:
>> >> I see there are some updates retargetting JIRA version at 2.5.1 from
>> >> 2.6.0. I think the changes on master are now more suited to the
>> >> release being versioned as 2.6.0. There are plenty of changes in the
>> >> time since 2.5.0 that would have suited 2.5.x releases, but there
>> >> seems to be enough others in there now that might better fit a 2.6.0
>> >> due to adding new functionality etc.
>> >>
>> >> Thoughts?
>> >>
>> >> Robbie
>> >>
>> >> On 26 April 2018 at 22:46, Clebert Suconic <
>> clebert.suco...@gmail.com> wrote:
>> >>> Little snafu today... I'm dealing with a failure in
>> >>>
>> org.apache.activemq.artemis.tests.integration.openwire.amq.RedeliveryPolicyTest.testRedeliveryPolicyPerDestination
>> >>>
>> >>> will send the vote soon.
>> >>>
>> >>> On Wed, Apr 25, 2018 at 9:24 PM, Clebert Suconic
>> >>>  wrote:
>>  I will cut it tomorrow.  I won’t merge anything until it’s out.
>> 
>>  @Commiters please don’t break Anything today :)
>> 
>>  @everyvody if there is anything you want Merged or committed
>> tomorrow let me
>>  know.
>> 
>>  On Wed, Apr 25, 2018 at 4:41 PM pwjenkins
>>   wrote:
>> > Are you on track to release by the end of April?
>> >
>> >
>> >
>> 

[GitHub] activemq-artemis issue #2089: ARTEMIS-1866: Make Quorum vote result wait tim...

[franz1981]

Github user franz1981 commented on the issue:

https://github.com/apache/activemq-artemis/pull/2089
  
@RaiSaurabh In addition, I have notived the both `ReplicaPolicy` and 
`ReplicatedPolicy` have `quorumVoteWait` mutable and not final, while they are 
not supposed to change that value after construction.


---

Re: [DISCUSS] Commits report

[Robbie Gemmell]

I think the report is nice, consolidating the details as it does. Its
worth saying much of it is essentially available live via the JIRA
release notes though given appropriate JIRA/commit handling.

When you mention "the release report", do you mean the announcement
email? If so I dont think including it would be an issue, though I
probably wouldnt as the existing JIRA based release notes output (e.g
http://activemq.apache.org/artemis/release-notes-2.5.0.html) seems
more suited for typical user needs to me than this, which feels like
it would be more useful to e.g the community before/during the vote.

I dont think it should be put on the mirrors however, which it
currently would be if left in the location it is now and the release
is published in the prior manner. Putting it on the website seems more
appropriate. If it is to be put on the mirrors however its essentially
'released' and so likely needs some licensing information added as the
HTML has none (though it is generated, so that may be ok) and the js
files distributed alongside dont detail any other than URLs which isnt
sufficient. The css at least mentions the names along with its URLs,
but thats perhaps not sufficient either.

Robbie

On 17 May 2018 at 03:52, Clebert Suconic  wrote:
> Before someone asks on the VOTE Thread.. I wanted to point out that I
> made a small project to parse git commit and generate a report.
>
> I have ran the report on top of artemis and I'm adding a commit report
> here that can be useful at least on the voter's thread:
>
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0/artemis-2.6.0.html
>
>
>
> I think it would be useful to have this one on top of the release
> report as well. If nobody opposes I would like to add it to the next
> release report.
>
> The report generator current lives on my github page but it could be
> moved somewhere else if someone bothers about being on my github fork:
>
> https://github.com/clebertsuconic/git-release-report
>
> --
> Clebert Suconic

[GitHub] activemq-artemis issue #2089: ARTEMIS-1866: Make Quorum vote result wait tim...

[franz1981]

Github user franz1981 commented on the issue:

https://github.com/apache/activemq-artemis/pull/2089
  
@RaiSaurabh We have an [hacking 
guide](https://activemq.apache.org/artemis/docs/latest/hacking-guide/code.html) 
that explain:

> When you commit your changes you will need to supply a commit message. We 
follow the 50/72 git commit message format. An ActiveMQ Artemis commit message 
should be formatted in the following manner:
> 
> Add the ARTEMIS JIRA (if one exists) followed by a brief description of 
the change in the first line. This line should be limited to 50 characters.
> Insert a single blank line after the first line.
> Provide a detailed description of the change in the following lines, 
breaking paragraphs where needed. These lines should be wrapped at 72 
characters.
> An example correctly formatted commit message:
> 
>   ARTEMIS-123 Add new commit msg format to README
> 
>   Adds a description of the new commit message format as well as examples
>   of well formatted commit messages to the README.md.  This is required 
>   to enable developers to quickly identify what the commit is intended to 
>   do and why the commit was added.


---

Re: [DISCUSS] Commits report

[Clebert Suconic]

I meant the announcement email.  And the report staying along with the
release notes as you said.  Not on the mirrors no.


On Thu, May 17, 2018 at 7:29 AM Robbie Gemmell 
wrote:

> I think the report is nice, consolidating the details as it does. Its
> worth saying much of it is essentially available live via the JIRA
> release notes though given appropriate JIRA/commit handling.
>
> When you mention "the release report", do you mean the announcement
> email? If so I dont think including it would be an issue, though I
> probably wouldnt as the existing JIRA based release notes output (e.g
> http://activemq.apache.org/artemis/release-notes-2.5.0.html) seems
> more suited for typical user needs to me than this, which feels like
> it would be more useful to e.g the community before/during the vote.
>
> I dont think it should be put on the mirrors however, which it
> currently would be if left in the location it is now and the release
> is published in the prior manner. Putting it on the website seems more
> appropriate. If it is to be put on the mirrors however its essentially
> 'released' and so likely needs some licensing information added as the
> HTML has none (though it is generated, so that may be ok) and the js
> files distributed alongside dont detail any other than URLs which isnt
> sufficient. The css at least mentions the names along with its URLs,
> but thats perhaps not sufficient either.
>
> Robbie
>
> On 17 May 2018 at 03:52, Clebert Suconic 
> wrote:
> > Before someone asks on the VOTE Thread.. I wanted to point out that I
> > made a small project to parse git commit and generate a report.
> >
> > I have ran the report on top of artemis and I'm adding a commit report
> > here that can be useful at least on the voter's thread:
> >
> >
> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0/artemis-2.6.0.html
> >
> >
> >
> > I think it would be useful to have this one on top of the release
> > report as well. If nobody opposes I would like to add it to the next
> > release report.
> >
> > The report generator current lives on my github page but it could be
> > moved somewhere else if someone bothers about being on my github fork:
> >
> > https://github.com/clebertsuconic/git-release-report
> >
> > --
> > Clebert Suconic
>
-- 
Clebert Suconic

[GitHub] activemq-artemis issue #2089: ARTEMIS-1866: Make Quorum vote result wait tim...

[RaiSaurabh]

Github user RaiSaurabh commented on the issue:

https://github.com/apache/activemq-artemis/pull/2089
  
@franz1981 I have updated it. Refer the image

![image](https://user-images.githubusercontent.com/22483381/40176581-795ca33a-59f9-11e8-9209-6c66da5c286c.png)



---

[GitHub] activemq-artemis issue #2089: ARTEMIS-1866: Make Quorum vote result wait tim...

[franz1981]

Github user franz1981 commented on the issue:

https://github.com/apache/activemq-artemis/pull/2089
  
@RaiSaurabh I can't see any changes on the commit message or am I reading 
the old one?


---

[GitHub] activemq-artemis issue #2089: ARTEMIS-1866: Make Quorum vote result wait tim...

[RaiSaurabh]

Github user RaiSaurabh commented on the issue:

https://github.com/apache/activemq-artemis/pull/2089
  
@franz1981 I have updated the code as per your suggestion and also updated 
the commit message same as the PR. Could you please review.


---

Re: [HEADS-UP] 2.5.1 in one week

[Clebert Suconic]

It was my fault. I kept finding last minute issues and postponed the
release over and over.

I will avoid that next time I do a release.

Sorry about that.

On Thu, May 17, 2018 at 7:51 AM Robbie Gemmell 
wrote:

> It was clear a release was coming at some point, however I think Tim's
> mail is more around that it was actually not clear precisely when it
> would, and so a notice would have been nice. If anything the mail
> thread made it less clear when it would arrive, given it had been
> coming for several weeks and the previous mail was 6 days before the
> one saying you had tagged it.
>
> I have no issue with lack of heads up mail in general, especially when
> its well understood the point it will release (e.g JIRAs assigned
> being resolved) or releases are frequent enough it simply becomes much
> less important, but I also think it would have been good in this case
> given the several prior heads ups served to somewhat mislead.
>
> On 16 May 2018 at 17:32, Clebert Suconic 
> wrote:
> > I have been pushing this for a few weeks.  I thought it was more than
> > clear.  I didn’t mean to get anyone by surprise.
> >
> > Along the conversation here 2.5.1 will just be renamed as 2.6.0.
> >
> >
> > I’m traveling today and I wanted to tag and upload from home.  And I
> wanted
> > something to do tonight at the hotel :).  Sorry for any trouble.
> >
> > We can try another one shortly in a few weeks. (2 or 3)
> >
> > On Wed, May 16, 2018 at 11:53 AM Timothy Bish 
> wrote:
> >
> >> On 05/16/2018 11:09 AM, Clebert Suconic wrote:
> >> > I just tagged as 2.6.0... It's uploading...
> >> >
> >> > I will cleanup JIRA tonight / tomorrow.. should send the voting thread
> >> > soon (tonight or tomorrow)
> >>
> >> This seems a bit backwards to me.  I'd think in the future it'd be nice
> >> to send some notice before you spin the release to give folks some
> >> warning.  The title of this thread still references a 2.5.1 release in a
> >> week which are both incorrect so anyone watching for it might miss the
> >> notice and anyone working on last minute fixes or whatnot gets no
> notice.
> >>
> >> It'd probably be a good idea to do the JIRA cleanup prior to all this as
> >> a way to better gauge where things stand before pulling the trigger and
> >> also give people some better insight into what is in the release when
> >> the vote thread appears.
> >>
> >> It probably wouldn't be as big a deal if releases were happening on a
> >> more frequent basis but given the long delay I'd say some warning next
> >> time would probably be the courteous thing to do.
> >>
> >> > On Thu, May 10, 2018 at 10:33 AM, Clebert Suconic
> >> >  wrote:
> >> >> I have been clearing the testsuite. Other guys are working with me on
> >> >> that (Francesco, Justin for instance). I'll do as soon as I'm done.
> >> >>
> >> >> On Thu, May 10, 2018 at 8:24 AM, Christopher Shannon
> >> >>  wrote:
> >> >>> +1 to make this a 2.6.0 release, there are now over 80 commits and
> >> >>> been enough time that I think a 2.6.0 makes more sense
> >> >>>
> >> >>> On Thu, May 3, 2018 at 12:09 PM, Clebert Suconic
> >> >>>  wrote:
> >>  Meanwhile please set your fixes as 2.5.1... i will rename it as
> 2.6.0
> >>  before releasing as everything is already filtered there.
> >> 
> >>  On Thu, May 3, 2018 at 12:04 PM, Clebert Suconic
> >>   wrote:
> >> >  From the entire set.. we only have fixes.. and 4 enhancements...
> >> > (previously existent features).
> >> >
> >> > I would prefer saving 2.6.0 for a more substantial release.. but
> if
> >> > you guys still prefer calling 2.6.0 I'm fine with that.
> >> >
> >> > On Thu, May 3, 2018 at 11:02 AM, Robbie Gemmell
> >> >  wrote:
> >> >> I see there are some updates retargetting JIRA version at 2.5.1
> from
> >> >> 2.6.0. I think the changes on master are now more suited to the
> >> >> release being versioned as 2.6.0. There are plenty of changes in
> the
> >> >> time since 2.5.0 that would have suited 2.5.x releases, but there
> >> >> seems to be enough others in there now that might better fit a
> 2.6.0
> >> >> due to adding new functionality etc.
> >> >>
> >> >> Thoughts?
> >> >>
> >> >> Robbie
> >> >>
> >> >> On 26 April 2018 at 22:46, Clebert Suconic <
> >> clebert.suco...@gmail.com> wrote:
> >> >>> Little snafu today... I'm dealing with a failure in
> >> >>>
> >>
> org.apache.activemq.artemis.tests.integration.openwire.amq.RedeliveryPolicyTest.testRedeliveryPolicyPerDestination
> >> >>>
> >> >>> will send the vote soon.
> >> >>>
> >> >>> On Wed, Apr 25, 2018 at 9:24 PM, Clebert Suconic
> >> >>>  wrote:
> >>  I will cut it tomorrow.  I won’t merge 

Re: [VOTE] Apache ActiveMQ 5.15.4

[Jean-Baptiste Onofré]

+1

Regards
JB

Le 17 mai 2018 à 20:15, à 20:15, Christopher Shannon 
 a écrit:
>Hi Everyone,
>
>I have created the ActiveMQ 5.15.4 release and it's ready for a vote.
>This
>release includes 10 fixes/improvements.
>
>The list of resolved issues is here:
>https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12342685
>
>You can get the release artifacts here:
>https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.4/
>
>Maven repository is at:
>https://repository.apache.org/content/repositories/orgapacheactivemq-1158/
>
>Source tag:
>https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=165cba235a915cdd40f1735918d646df9a49e521
>
>Please vote to approve this release.  The vote will remain open for 72
>hours.
>
>[ ] +1 Release the binary as Apache ActiveMQ 5.15.4
>[ ] -1 (provide specific comments)
>
>Here's my +1

[VOTE] Apache ActiveMQ 5.15.4

[Christopher Shannon]

Hi Everyone,

I have created the ActiveMQ 5.15.4 release and it's ready for a vote.  This
release includes 10 fixes/improvements.

The list of resolved issues is here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12342685

You can get the release artifacts here:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.4/

Maven repository is at:
https://repository.apache.org/content/repositories/orgapacheactivemq-1158/

Source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=165cba235a915cdd40f1735918d646df9a49e521

Please vote to approve this release.  The vote will remain open for 72
hours.

[ ] +1 Release the binary as Apache ActiveMQ 5.15.4
[ ] -1 (provide specific comments)

Here's my +1

Re: [VOTE] Apache ActiveMQ 5.15.4

[Ragnar Paulson]

+1 (non-binding)

Ragnar

On Thu, May 17, 2018 at 2:15 PM, Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:

> Hi Everyone,
>
> I have created the ActiveMQ 5.15.4 release and it's ready for a vote.  This
> release includes 10 fixes/improvements.
>
> The list of resolved issues is here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12311210=12342685
>
> You can get the release artifacts here:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.4/
>
> Maven repository is at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1158/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=
> 165cba235a915cdd40f1735918d646df9a49e521
>
> Please vote to approve this release.  The vote will remain open for 72
> hours.
>
> [ ] +1 Release the binary as Apache ActiveMQ 5.15.4
> [ ] -1 (provide specific comments)
>
> Here's my +1
>

Re: [VOTE] Apache ActiveMQ Artemis 2.6.0

[Christopher Shannon]

+1

On Thu, May 17, 2018 at 2:51 PM, Timothy Bish  wrote:

> On 05/16/2018 10:49 PM, Clebert Suconic wrote:
>
>> I would like to propose an Apache ActiveMQ Artemis 2.6.0 release.
>>
>> The release notes can be found here:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?versi
>> on=12342903&=12315920
>>
>> There is a new commits report I made that I'm introducing on this release:
>> https://dist.apache.org/repos/dist/dev/activemq/activemq-art
>> emis/2.6.0/artemis-2.6.0.html
>>
>> Source and binary distributions can be found here:
>> https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0
>>
>> The Maven repository is here:
>> https://repository.apache.org/content/repositories/orgapacheactivemq-1157
>>
>> In case you want to give it a try with the maven repo on examples:
>> http://activemq.apache.org/artemis/docs/latest/hacking-guide
>> /validating-releases.html
>>
>> The source tag:
>> https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.g
>> it;a=tag;h=refs/tags/2.6.0
>>
>> I will update the website after the vote has passed.
>>
>>
>> [ ] +1 approve the release as Apache Artemis 2.4.0
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>>
>>
>> Here's my +1
>> .
>>
>>
> +1
>
> * Validate the signatures and checksums
> * Review license and notice files in the archives
> * Build from source and ran some of the tests
> * Ran binary broker and ran some samples and performance tests against it
> * Used mvn apache-rat:check to validate license headers in place
>
>
> --
> Tim Bish
> twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>

Re: [VOTE] Apache ActiveMQ 5.15.4

[Clebert Suconic]

+1

Regards

On Thu, May 17, 2018 at 2:46 PM, Ragnar Paulson  wrote:
> +1 (non-binding)
>
> Ragnar
>
> On Thu, May 17, 2018 at 2:15 PM, Christopher Shannon <
> christopher.l.shan...@gmail.com> wrote:
>
>> Hi Everyone,
>>
>> I have created the ActiveMQ 5.15.4 release and it's ready for a vote.  This
>> release includes 10 fixes/improvements.
>>
>> The list of resolved issues is here:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> projectId=12311210=12342685
>>
>> You can get the release artifacts here:
>> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.4/
>>
>> Maven repository is at:
>> https://repository.apache.org/content/repositories/orgapacheactivemq-1158/
>>
>> Source tag:
>> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=
>> 165cba235a915cdd40f1735918d646df9a49e521
>>
>> Please vote to approve this release.  The vote will remain open for 72
>> hours.
>>
>> [ ] +1 Release the binary as Apache ActiveMQ 5.15.4
>> [ ] -1 (provide specific comments)
>>
>> Here's my +1
>>



-- 
Clebert Suconic

Re: [VOTE] Apache ActiveMQ 5.15.4

[Timothy Bish]

On 05/17/2018 02:15 PM, Christopher Shannon wrote:

Hi Everyone,

I have created the ActiveMQ 5.15.4 release and it's ready for a vote.  This
release includes 10 fixes/improvements.

The list of resolved issues is here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12342685

You can get the release artifacts here:
https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.4/

Maven repository is at:
https://repository.apache.org/content/repositories/orgapacheactivemq-1158/

Source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=165cba235a915cdd40f1735918d646df9a49e521

Please vote to approve this release.  The vote will remain open for 72
hours.

[ ] +1 Release the binary as Apache ActiveMQ 5.15.4
[ ] -1 (provide specific comments)

Here's my +1



+1

* Validated signatures and checksums
* Validated license and notice files in archives
* Built from source and ran the smoke tests
* Ran the binary broker and tested using an AMQP perf tool
* Ran mvn apache-rat:heck to look for missing license headers


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/

[GitHub] activemq-artemis pull request #2092: ARTEMIS-1853 Adding Netty OpenSSL provi...

[gaohoward]

GitHub user gaohoward opened a pull request:

https://github.com/apache/activemq-artemis/pull/2092

ARTEMIS-1853 Adding Netty OpenSSL provider test

Added some netty openssl tests
Fix a NPE issue

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gaohoward/activemq-artemis g_openssl2

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/2092.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2092


commit 246e32d0a1854ce40cabb8e2b3b38344ab532ad6
Author: Howard Gao 
Date:   2018-05-17T22:50:37Z

ARTEMIS-1853 Adding Netty OpenSSL provider test

Added some netty openssl tests
Fix a NPE issue




---

Re: [VOTE] Apache ActiveMQ Artemis 2.6.0

[Timothy Bish]

On 05/16/2018 10:49 PM, Clebert Suconic wrote:

I would like to propose an Apache ActiveMQ Artemis 2.6.0 release.

The release notes can be found here:

https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342903&=12315920

There is a new commits report I made that I'm introducing on this release:
https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0/artemis-2.6.0.html

Source and binary distributions can be found here:
https://dist.apache.org/repos/dist/dev/activemq/activemq-artemis/2.6.0

The Maven repository is here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1157

In case you want to give it a try with the maven repo on examples:
http://activemq.apache.org/artemis/docs/latest/hacking-guide/validating-releases.html

The source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;a=tag;h=refs/tags/2.6.0

I will update the website after the vote has passed.


[ ] +1 approve the release as Apache Artemis 2.4.0
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)


Here's my +1
.



+1

* Validate the signatures and checksums
* Review license and notice files in the archives
* Build from source and ran some of the tests
* Ran binary broker and ran some samples and performance tests against it
* Used mvn apache-rat:check to validate license headers in place


--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/

Re: [VOTE] Apache ActiveMQ 5.15.4

[Francois Papon]

+1 (non-binding)

Thanks !

François


Le 17/05/2018 à 22:15, Christopher Shannon a écrit :
> Hi Everyone,
>
> I have created the ActiveMQ 5.15.4 release and it's ready for a vote.  This
> release includes 10 fixes/improvements.
>
> The list of resolved issues is here:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210=12342685
>
> You can get the release artifacts here:
> https://dist.apache.org/repos/dist/dev/activemq/activemq/5.15.4/
>
> Maven repository is at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1158/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=165cba235a915cdd40f1735918d646df9a49e521
>
> Please vote to approve this release.  The vote will remain open for 72
> hours.
>
> [ ] +1 Release the binary as Apache ActiveMQ 5.15.4
> [ ] -1 (provide specific comments)
>
> Here's my +1
>

Re: Join to the group

[Arthur Naseef]

Hey Alexander - pull requests can be submitted by anybody via github; no
special permissions needed.

By "create issues" - do you mean on github, or jira?  For github, I believe
it's open.  For Jira, I would need to research whether non-Apache folks can
create Jira entries, and what it would take to enable.

Art


On Sun, May 13, 2018 at 7:48 AM, Alexander Savonin 
wrote:

> Hello. I'm an active user of the activemq in my company.
> Could i join to create issues and send pull requests?
> Thank you!
>