Branch for v2 changes?

[Steve Brewin <sb...@synsys.com>]

Hi,

Now we have branches build_2_2_0_RC and build_2_1_fcs, to which should I
commit the MimeMultipart/report related changes to?

I sure don't want to screw up all the excellent work Noel has done in
preparing the release canidate!

Cheers,

-- Steve


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

RE: Branch for v2 changes?

["Noel J. Bergman" <no...@devtech.com>]

> Now we have branches build_2_2_0_RC and build_2_1_fcs, to which
> should I commit the MimeMultipart/report related changes to?

The branch is branch_2_1_fcs.  The build_* labels are just tags.  Since this
is a release candidate, I tagged CVS so that we could always check it out.

I believe that if I want to tag everything currently tagged as
build_2_2_0_RC1 as build_2_2_0, I issue:

 cvs tag -r build_2_2_0_RC1 build_2_2_0

I assume that if new code is committed and we need to make a bug fix without
including all of the new code, that we issue the aforementioned command, and
then explicitly tag the file(s) containing the bug fix.

	--- Noel


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org