Re: code promotion / changeset deployment process - best practices?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mar 15, 2005, at 11:22 PM, oleksa borodie wrote:

>> I'd recommend this:
>>
>> trunk
>> branches
>> issues
>> issue(id)
>> maintenance
>> maint(id)
>> tags
>> trunk(id)
>> maint(id)
>
> Could you give me the difference between 'issue' and 'maint' please.
> I thought that developers work on the branch together and merge
> changes to trunk.

The issue branch structure is formally known as a task branch. It
isolates
a single set of changes for a particular task, which makes it easy to
integrate certain fixes or enhancements into the trunk or maintenance
branches.

This allows for developers to commit as often as they like without
polluting
the trunk with code that hasn't been reviewed and/or doesn't work. Only
after
review or testing do the changes get integrated into trunk or maint
lines.

The trunk would be the most current "best" integration. maint branches
would
be made immediately upon or slightly in advance of a release, allowing
the
trunk to stay active for future development.

> Is there any 'The best practice of' concurrent develepment with
> Subversion?

Well, there are several books written a long time ago that work as well
for
Subversion as they do for any other versioning system.

One that I really like, by a participant of this mailing list no less:

http://www.amazon.com/exec/obidos/tg/detail/-/0201741172/102-2379156
- -7960160?v=glance

- --
- -- Tom Mornini
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFCOGn1zaKkuvKwKvcRApcfAJ9sxZWH/N3BFPHFe0f99yZKkfHagwCfV9fR
t3izGGZIYe6/lhWo95yK0bw=
=+VjL
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 16 18:21:57 2005