On Thu, 4 Mar 2004 18:56:41 -0300
"Luiz Daniel Lapolla" <email@example.com> wrote:
> We are considering the adoption of a branch-by-task model:
> - A new branch (across all files) is created for each Change
> based on the last stable milestone.
> - All the development for one CR goes on it's own branch.
> - After N cicles of testing and bugfixing the branch is scheduled
> to be
> merged with it's baseline.
This is the development model we're currently using. Performance seems
to be good, but we've not really been using SVN long enough to get solid
One caveat is that merging the whole branch back is a bit different than
in CVS (you have to specify the starting revision of the branch). It's
not that it's any more difficult, it's just that it's different enough
that it's easy to make mistakes until you get the hang of it (the first
few times I did it nearly drove me to distraction). Once you get used
to it it though, it's not any harder than under CVS and has some
home: firstname.lastname@example.org jabber: email@example.com
work: firstname.lastname@example.org ms msg: email@example.com
pgp id: 1ECBCC78
Received on Thu Mar 4 23:19:20 2004
- application/pgp-signature attachment: stored