activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kevin Burton <bur...@spinn3r.com>
Subject Re: My pull requests haven’t been merged?
Date Fri, 06 Mar 2015 01:52:27 GMT
Crap.  No I didn’t :-P … I didn’t realize there was going to be a 5.12.x
branch and that I should have preferred that.  So I’ll rework this.  I
think it will probably just be easily cherry picked though.

On Thu, Mar 5, 2015 at 1:30 PM, Tim Bain <tbain@alumni.duke.edu> wrote:

> Did you also submit pull requests for them into 5.12.x as well?  My
> impression (as a non-committer just observing the process) is that
> generally fixes get merged into the new version first and foremost, and
> only back-ported into a maintenance release if they're deemed important
> enough (and if there are enough such fixes to warrant a maintenance
> release, which generally seems to be avoided if possible).  But I may be
> misinterpreting what I've observed as a non-participant in the process.
>
> Tim
>
> On Thu, Mar 5, 2015 at 12:56 PM, Kevin Burton <burton@spinn3r.com> wrote:
>
> > I have two outstanding pull requests for 5.11.x that haven’t been merged.
> >
> > https://github.com/apache/activemq/pull/65
> >
> > https://github.com/apache/activemq/pull/64
> >
> > What do I have to do to get these merged?  I haven’t received any
> feedback
> > on them but have seen other merge requests closed.
> >
> > I don’t want these to be left behind as they fix important scalability
> > issues in ActiveMQ
> >
> > --
> >
> > Founder/CEO Spinn3r.com
> > Location: *San Francisco, CA*
> > blog: http://burtonator.wordpress.com
> > … or check out my Google+ profile
> > <https://plus.google.com/102718274791889610666/posts>
> > <http://spinn3r.com>
> >
>



-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>
<http://spinn3r.com>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message