activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruce Snyder <>
Subject Re: [VOTE] ActiveMQ 5.3.0
Date Fri, 18 Sep 2009 00:23:47 GMT
On Thu, Sep 17, 2009 at 4:24 PM, Hiram Chirino <> wrote:

> It's been deployed to a staging repo.  See my earlier reply about that in
> this thread.

Then we should probably vote on and release that module separately and
before the full ActiveMQ release. The ActiveMQ release candidates
shouldn't make use of candidate modules located in temporary repos.

>> Also, why has there been no discussion regarding the preparation for
>> this release on the dev list?
> Isn't that what what's going on now?
> IMHO rolling release candidates is the best way to get folks engaged and
> discussing the current state of the product and whats still missing.


> As we have long seen in the History of ActiveMQ releases.. it typically
> takes several release candidates before everyone's happy.  I guess this
> first release candidate was no different!

Agreed, release candidates are the best way to seek consensus for a
release. To improve upon the way we go about handling releases, I'd
like to suggest a couple minor changes:

* Since tags are supposed to be a snapshot in time and therefore
shouldn't change, I'd like to suggest that the tag name be changed to
reflect the fact that it's a release candidate, e.g.,
activemq-5.3.0-RC1, etc. Either that or we could instead work from a
branch that can change as much as necessary until there's agreement on
which candidate to release.

* I'd also like to suggest that tarballs and zips for each release
candidate be labeled as such, e.g.,
apache-activemq-5.3.0-RC2-bin.tar.gz, etc. This way there is no
confusion and downloaded items are clearly marked as a release
candidate and not a full 5.3 release.

Also, while we're discussing releases, we should make sure that the
release guide reflects the latest practices:

I see that it needs to be updated to include the process for release

> That's why I'm grateful to anyone who take the initiative to start rolling
> the release candidates.  They are basically taking on a tough job and
> prodding the rest of to get involved the release!
> We really do need to start doing releases more often.

+1 to releasing more often. We should probably aim for more frequent
minor releases, i.e., 5.2.1, 5.2.2, etc. so fixes are delivered

perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"

ActiveMQ in Action:

View raw message