Is needed to create a branch for each release? Why not just tag them? On Thu, Mar 13, 2008 at 12:44 PM, Jesper Staun Hansen <[EMAIL PROTECTED]> wrote:
> I just commit my stuff, and keep a detailed changelog locally. > And releases I just commit to the download folder and keep on working on > the src folder. > > Onno Ekker wrote: > > Hi, > > > > Being new to CVS, I'd like to know how other people use it. > > > > I have a small project, which I develop alone, and at the moment I > > primarily use CVS to get the changes to > > www and src on the server. So basically all I do is CVS Commit (and > > Add/Ignore). > > > > For the project source it is probably better to start a new branch > > when starting or releasing a new version? > > That would allow you to more easily switch to an old version and see > > the diffs? > > But then you should always create a new branch > > PROJECT_<version#>_<release#>[_<patch#>] ? > > Would that make sense, or are there better (easier, more reliable,...) > > ways to manage your versions? > > > > Onno > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Project_owners mailing list > > [email protected] > > https://www.mozdev.org/mailman/listinfo/project_owners > > > > > _______________________________________________ > Project_owners mailing list > [email protected] > https://www.mozdev.org/mailman/listinfo/project_owners > -- ______ Ezequiel. Http://www.ironicnet.com
_______________________________________________ Project_owners mailing list [email protected] https://www.mozdev.org/mailman/listinfo/project_owners
