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

Tagging Policy Full & Patch Release

From: Lakshman Srilakshmanan <lakshman.srilakshmanan_at_tradingpost.com.au>
Date: 2006-02-21 07:02:53 CET

Hi All,

I would like to explain the tagging process I followed in CVS and would
much appreciate an alternative approach in Subversion.

When I do a full release of an application I tag the entire application
in CVS as Release_1_0_0
When I do a patch release of an application (ie 3 files) I tag the
entire application in CVS Release_1_0_1 and another tag Patch_1_0_1
containing ONLY the 3 files that will be released.

The rational behind this tagging policy is that I can re-create the
entire package based on Release_1_0_1 (if needed) and can apply only the
patch into production using Patch_1_0_1.

In Subversion I can create a full Release tag Release_1_0_1. But I don't
believe I can create a Patch_1_0_1 tag as described above. Or am I wrong

I would much appreciate your suggestion in this matter.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 21 07:03:48 2006

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.