Thx for help Jason. You got the idea :-)
Let's go ahead with this, thinking in this situation: I had a stable version 1.34 (subprojectA) and part of development team is working into a new features to version 1.35 ( trunk) but there is a bug happening in 1.34 , I'm reallocate one of developers to correct this, and he made some corrections on project/subprojectA/dir1/file1.py then he tag this file with 1.34.1 tag , I generate 1.34.1 and deploy to customer. After some time I had 1.35 ready to go. But on this time I want to send all subprojectA. What is correct way to do this. Just svn copy of trunk to tag 1.35?? and what can I do if in the future I want to regenerate subprojectA version 1.34.1 with full tree. This is my question. On 8/6/07, Jason Winnebeck <[EMAIL PROTECTED]> wrote: > > > I would read the SVN book > http://svnbook.red-bean.com/nightly/en/index.html and there it will tell > you about the standard "branches/tags/trunk" layout of the repository. > If you want to mark/make releases, the standard practice is to tag it. > To make a tag, just copy the trunk to a directory in tags. > (http://svnbook.red-bean.com/nightly/en/svn.branchmerge.tags.html). > Other organizations may use releases or QA branches, in that case you > want to tag from there. > > So, one possible model for deployment could be: > * Develop features for 1.0 in trunk > * When beta is ready, copy trunk to branches/release-1.0 > * QA tests and makes bug fixes to branches/release-1.0 > * Developers make new development features in trunk, towards 2.0 > release > * When QA says "1.0" is good, copy branches/release-1.0 to tags/1.0 > > Jason > > ________________________________________ > From: [email protected] [mailto:[EMAIL PROTECTED] > On Behalf Of Lucas Stephanou > > ... > Now, I'm thinking in a correct and efficient way to deploy and generate > versions to costumer. > ... > Well, how mark files to send in a determined version. > ... > > > > -- Lucas Stephanou --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
