Fabian Lange wrote: > Hi, > I think this makes sense. Please try to set up feature branches, preferably > on /branches/xyzFeature. And I would recommend to branch the whole tree > unless hard disk is an issue :-) So that in case you find you need to modify > code somewhere completely unrelated, it wont get messy.
yes. > > On the other hand, I admit, that creating many branches can also be messy. > So I don’t think that branches should be mandatory for everything. If its > small, if its agreed and if its tested it can go directly into trunk/ > respectively branches1.2/ sure. To make things a bit clearer, I suggest to create a symfony 1.2 branch for Kris to work on migrations for example. Fabien > > .:Fabian > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[EMAIL PROTECTED] Im > Auftrag von Fabien Potencier > Gesendet: Montag, 25. August 2008 21:18 > An: [email protected] > Betreff: [symfony-devs] Re: sfPropelPlugin 1.3 behaviors rewritten > > > Thanks. I think it makes more sense to create one branch per main > feature you want to work on. That way, other people can help you out and > when we will need to merge back to trunk, we will be able to do that > feature by feature. Is it possible? > > Fabien > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
