On 5/15/07, AJ Mercer <[EMAIL PROTECTED]> wrote: > OK, irrespective of whether the trunk or branches are used > how do you selectively chose what you want to deploy?
Now we're into build management :) Which is mostly outside subversion, but the basic way subversion can support you process is by tagging revisions -- the basic pattern is to create a directory parallel to /trunk called /tags and then copy whatever is being release (eg /trunk) to a tag. Then you can always use the tag to checkout code that represents a particular release. Even when you're at REL-5.0, your tag for REL-2.1 points to the proper revisions of the codebase and you can checkout from the tag (or from a branch if you choose to use release branches in addition to tags) > If I have 5 bug fixes on the go bug001 - bug005, > and bug004 is signed off > how would I use subversion to know which files need to be updated on > production (without any of the work on bugs 1,2,3,5 going over)? Merge bug004 into whatever the "main" branch is, which is probably either trunk or a release branch, tag the resulting version as a release, and export the release. -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion?sdid=RVJV Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:278148 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
