Hi, this sounds just the kind of branching that Git, Mercurial and other distributed version control systems are famous for.
I know that both Mercurial and Git have SVN importers that are able to sync SVN <-> Git | Hg. There was a post in the code.google.com blog about this. The merging of a complex project as ArgoUML should be difficult even with these, with SVN it should be nightmarish! My 0.02 € Luís Marcus Vinícius de Ávila Couto wrote: > Hi Linus, > > In that first moment I guess I better keep things separate it in order to > mature the ideas about creating a software product line to ArgoUML. After the > maturation of ArgoUML-SPL can be that is more interesting to create it as a > branch of the same ArgoUML. In the beginning I do not think there will be > gains because we are still evaluating which technology that will be better to > our propose. > > I know that the future merges will be more complicated, but this will be the > price to be paid to the maturing of the technique that we develop. I think > the mix the maturation of our technology and constant merges with the trunk > tree of ArgoUML can disturb and confuse the process of maturation of > ArgoUML-SPL. I think it's better prorogue this action a little. > > Regards, > > Marcus Vinícius > > >> Since the argouml-spl project contain the whole of the source, should we set >> it up as a set of branches of the main project (each of the projects) >> instead? That would simplify any merging of features (both ways). >> >> /Linus >> ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2589666 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
