Hi Rich, You need to consider using branches. These let you isolate a set of changes from the trunk. A branch can be developed and tested and QA'd separately then when signed off can be merged back to the trunk. At this point it does need retesting because of an subsequent changes. Small issues can be fixed on the trunk. You then tag the trunk at a stable point for a release of one or more merged changes. This way different changes can be merged only when they are ready and until then stay on their branch.
This is how we work and our pattern of releases sounds similar to you. There are other patterns for using branches that suit other development modes. BTW Eclipse makes the merges nice and easy! On 3/27/06, Rich Kroll <[EMAIL PROTECTED]> wrote: > > Hello all, > We are currently working on implementing a new source control system and > are > turning to SVN as our original VSS system was not meeting out needs. We > -- Mike T Blog http://www.socialpoints.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:236272 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
