--- Shah Amit <[EMAIL PROTECTED]> wrote: > Hi, > > Please pardon my inexperience with > branching/labelling. I have a set of > requirements and I am confused as to how I can use > sourcejammer to help me. > > I have a project checked into sourcejammer. Let us > say there are 10 files in > that. Now I want to "release" versions 1.0. Do some > changes to the main line > of code and release 2.0, and similarly 3.0. However > after 3.0 is released, I > might want to be able to go into 1.0 and change > something in one of the > files (may be to fix some minor bugs) > > I tried to use label, but label doesn't let me > change any files "in" that > label, except if I rebuild the label. However in my > situation, I might > already be at version 3.0 and the code has > drastically changed compared to > version 1.0 (The root of the problem is, the > developement is far ahead of > the release schedule so we are releasing only small > portions of whatever is > ready !!) > > I tried to use the branch feature, but it says I > should share a file to > branch. Now I dont really need to share a file > because all i want to do is > "release" ?? > > Please advise ... > > Thanks, > Amit > This is something which Surround SCM from Seapine software handles very well. I think Source Jammer should take some ideas from it in this regard. It's the best source control system I have used for it's price. There are evaluations freely available for it which could be used to make the modifications to Source Jammer or to at least get the main ideas to put into some type of a design or concept document for future development.
Wade ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ SourceJammer-users mailing list SourceJammer-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sourcejammer-users
