incubator-ctakes-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Masanz, James J." <Masanz.Ja...@mayo.edu>
Subject RE: technical release process questions
Date Wed, 31 Oct 2012 15:34:06 GMT
I like the idea of building from trunk (with an announcement first) and the idea of "if we
ever need to patch an existing release, we can create a patch branch from the tag"

-- James


> -----Original Message-----
> From: ctakes-dev-return-777-Masanz.James=mayo.edu@incubator.apache.org
> [mailto:ctakes-dev-return-777-
> Masanz.James=mayo.edu@incubator.apache.org] On Behalf Of Chen, Pei
> Sent: Wednesday, October 31, 2012 9:44 AM
> To: ctakes-dev@incubator.apache.org
> Subject: RE: technical release process questions
> 
> > Ok, so you're just cutting the release directly from trunk then. In
> > that case, perhaps there should be a "Trunk is frozen" announcement,
> > where we warn developers not to commit anything? I imagine we don't
> > want random changes sneaking in while you're in the middle of the
> release process.
> 
> Yes, I think this was just an oversight on my part as I was just trying
> the new release process at ASF (And I wasn't too concerned about new
> changes in trunk getting into the RC at that time yet; manually
> reviewing all the commits that were happening).
> Going forward, Yes, I think we should make an explicit announcement to
> ctakes-dev about the upcoming release (candidate) that is about to be
> cut from trunk.
> I think it's probably a good idea to make the announcement regardless
> anyway to make the developers aware of what is going on (and just in
> case they actually would like something to be included but just needed
> some more time).
> 
> --Pei
> 
> > -----Original Message-----
> > From: Steven Bethard [mailto:steven.bethard@Colorado.EDU]
> > Sent: Wednesday, October 31, 2012 10:37 AM
> > To: ctakes-dev@incubator.apache.org
> > Subject: Re: technical release process questions
> >
> > On Oct 31, 2012, at 3:29 PM, "Chen, Pei"
> > <Pei.Chen@childrens.harvard.edu>
> > wrote:
> > >> (1) When we decide to make a release, does someone create a branch
> > >> for the release? I'm assuming yes, because otherwise there needs to
> > >> be some way of freezing development on the trunk. Where can I find
> > >> that
> > branch?
> > > By default, the mvn release plugin automatically always creates a
> > > tag by
> > default(example 3.0.0-incubating, etc.).
> > > Code is checked out and built from this tag for distribution.
> > > The tag could be treated as a frozen version when it was cut from
> > > trunk and
> > the release number is incremented in trunk for future development.
> >
> > Ok, so you're just cutting the release directly from trunk then. In
> > that case, perhaps there should be a "Trunk is frozen" announcement,
> > where we warn developers not to commit anything? I imagine we don't
> > want random changes sneaking in while you're in the middle of the
> release process.
> >
> > The alternative is to branch first, and cut the release from the
> > branch. Maven release will still create the same tag, but it will
> > create it from the branch instead of the trunk. This approach wouldn't
> require the "frozen"
> > announcement, and people could keep working from trunk.
> >
> > Steve

Mime
View raw message