activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet" <gno...@gmail.com>
Subject Re: Streamlining the ActiveMQ release process
Date Wed, 26 Jul 2006 20:47:53 GMT
True.
So we must either:
   * change our release process to the maven practice, i.e. vote on
snapshots and then release
   * find a nice way to release things and document it.

Also note that our release process is somehow problematic.
The way I did in ServiceMix and Xbean was to deploy the release to a private
remote repository at Apache.
But when the release is approved, you have to put the content of the repo in
the public Apache repositories
(at least for XBean, because ServiceMix and ActiveMQ are still in
incubation).
But if you just copy things, some metadata on the repository are lost :(

>From what i heard, maven 2.1 should handle such a release process better,
but i'm not sure how.

Cheers,
Guillaume Nodet



On 7/26/06, Hiram Chirino <hiram@hiramchirino.com> wrote:
>
> I actually think the maven 2 release plugin is a bit of pain.  It's not
> built to follow our release process where we put up release candidates,
> hold
> a vote, then deploy the release binaries.  It also handles the branching
> and
> tagging very differently.
>
> On 7/26/06, James Strachan <james.strachan@gmail.com> wrote:
> >
> > Sounds cool with me. I guess once we get to 4.1 we can use the maven 2
> > release plugin to make this kinda stuff easier
> >
> > On 7/26/06, Hiram Chirino <hiram@hiramchirino.com> wrote:
> > > Hi,
> > >
> > > I just recently put up a ActiveMQ 4.0.2 release candidate for vote so
> > while
> > > it's fresh on my mind I'd like to see if anybody minds if I make a
> small
> > > tweak to the way we label our snapshot versions.  I'd like to either
> > change
> > > it to 4.0-SNAPSHOT or even 4.0.x-SNAPSHOT.
> > >
> > > The driver behind this change is that on the 4.0 branch, every time we
> > do a
> > > release (for example this 4.0.2 release), we have to remember to
> > increment
> > > the version on the branch on all the poms.  It's easy to forget to
> > change
> > > this and I don't see much value in changing the pom after every
> release.
> > >
> > > --
> > > Regards,
> > > Hiram
> > >
> > > Blog: http://hiramchirino.com
> > >
> > >
> >
> >
> > --
> >
> > James
> > -------
> > http://radio.weblogs.com/0112098/
> >
>
>
>
> --
> Regards,
> Hiram
>
> Blog: http://hiramchirino.com
>
>

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