Mailing-List: contact users-help@continuum.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@continuum.apache.org
Received-SPF: pass (athena.apache.org: domain of batkinson@usm.maine.edu
 designates 130.111.135.148 as permitted sender)
Message-Id: <493828530200009D0001F088@uct5.uct.usm.maine.edu>
Date: Thu, 04 Dec 2008 18:58:27 -0500
From: "Brent Atkinson" <batkinson@usm.maine.edu>
To: <users@continuum.apache.org>
Subject: Working with maintenance branches
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=__PartC4ECB8B3.0__="

--=__PartC4ECB8B3.0__=
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi,
=20
I am having trouble figuring out how to handle maintenance branches in =
continuum=20
and I haven't had much luck finding information on the subject. I think it =
might be
that I am missing some fundamental understanding of how the development =
flow
should work.
=20
Say I start a project at 1.0-SNAPSHOT and add it to continuum. I then =
release the
project using the release plugin functionality. The release is tagged at =
1.0 and the
next iteration starts as 1.1-SNAPSHOT. Now development continues on=20
1.1-SNAPSHOT, but we need to fix a nasty bug on the 1.0 version (to make =
1.0.1).
=20
Now, my guess is that I manually use release:branch to create a maintenance=
=20
branch called 1.0.X from a working copy of 1.0. Would I schedule this =
branch=20
in continuum and cut releases from it like I do the trunk?
=20
Brent Atkinson
batkinson@usm.maine.edu

--=__PartC4ECB8B3.0__=--