[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Release management policy fundamentals

From: Tom Mornini <tmornini_at_infomania.com>
Date: 2005-01-12 08:13:41 CET

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

Here's a good book, written by someone who reads this list. :-)

http://www.amazon.com/exec/obidos/ASIN/0201741172/103-5855470-7615011

On Jan 11, 2005, at 7:43 PM, Nick Patavalis wrote:

> The subversion book, the online manuals, as well as this mailing list,
> are excellent resources for learning how subversion works, and how you
> can command it to do what you want. What I have been unable to find,
> though, in printed or online material, are advices, discussions, or
> guidelines, about the fundamentals of revision management *policies*
> (as opposed to mere mechanics). Though policies naturally differ
> depending on the needs of a project, I do believe that for a spectrum
> of tasks (e.g. software release management) it would not be impossible
> to derive and classify a few sets of fundamental models, or so to say,
> "operational canons" upon which one could base the variations that
> suit the needs of a specific project.

- --
- -- Tom Mornini

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

iD8DBQFB5M4lzaKkuvKwKvcRAkjNAJ9Csfkx2u1J4LJCTO01SXEtHPFVPACfXjO4
89DouoDsCI52e2P918w8mLA=
=DIze
-----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 Jan 12 08:17:18 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.