-Original Message-
From: John Barstow [mailto:[EMAIL PROTECTED]
Sent: November 12, 2003 7:40 PM
To: Clayton Harbour
Subject: RE: [nant-dev] NAnt Tag and Branch policies
I can't post to the list from this account; please forward.
As the one who started dabbling with branches, my origina
Scott,
> The reason to keep branches to a min is that changes from one branch
to
> not
> affect another. So if we fix something in 0.8.3 branch, we also need
to
> fix
> all subsequent branches. Branches also require special changes to the
way
> we
> as developers work.
Sorry Scott, I am a little
Okay, I've just given some thought to how we use cvs to tag and branch our
releases. Here is what I think we should talk about adopting as our policy.
We should do the following...Lay down rtags (tags on the server) when we do
a release (or milestone/beta/rc). This will allow us to get back to tha
FYI:
- Original Message -
From: "John Barstow" <[EMAIL PROTECTED]>
> Sorry, can't post to the list with this account. Please forward.
>
> I've just created BRANCH-0-8-4 and updated the changelog. The code builds
> and tests cleanly.
> You can checkout, or update to, the branch by spec
Yep, I changed the nantcontrib stuff to match up wrt [FileSet] changes. What
is the status of the release plan? Who will be doing what, and when?
- Original Message -
From: "Gert Driesen" <[EMAIL PROTECTED]>
To: "John C Barstow" <[EMAIL PROTECTED]>; "Morris, Jason"
<[EMAIL PROTECTED]>; "N
