Ah, I don't think it makes sense to make a branch for every bug. > and it might be not clear at start towards what release it > will be targeted
The target release is not a problem if the development takes place in the trunk. > it probably would break everything in the project Remember: We can always go back and only working code should be checked in, so the mess up shouldn't be too much anyway. I don't see a big danger there. > suppose I got some stupid > idea that i am not even sure it make sense Develop it lokally and ask the list if it shall be added or not. I would ask prior to putting any effort in it. ;) Such a concept would only complicate the development process in my eyes and I still don't see a benefit. Cheers Joachim Am 02.09.2011 18:43, schrieb Vladimir Avdonin: > On 09/02/2011 11:25 AM, Joachim wrote: >> Hi, >> >> > I could think of three directories: fixes, features, users. >> >> Normally branches are made for different releases. I don't see >> a benefit in these three suggested branches as bug fixes have to >> be merged with new features anyway. The users branch is a concept >> I didn't get. >> > > Oh, those are not branches themselves, those would be just directories > to organize branches of similar purpose together. > > Probably use examples would help to justify. > > Fixes is easy one - each branch in there could be for an accepted bug in > bug tracker. It would leave there until the fix is tested and accepted > at which point changes merge to trunk and branch is deleted. > > Feature is also more or less clear. Say a major feature effort is > undertaken, like adding visual themes for example. Several people would > work on that, and it might be not clear at start towards what release it > will be targeted, or even when it would be completed. And at the > beginning it probably would break everything in the project. It will > eventually be implemented at which point it would merge to either trunk, > or pre-release brunch, and changes will be deleted. > > For users I would illustrate it like this - suppose I got some stupid > idea that i am not even sure it make sense, but I want to try it anyway. > Like, say, adding sequencer. It would not fit in features in my view, > because not everyone would agree that the project needs such feature at > all. The features would have only agreed lines of development. Users are > free to put anything in their personal branches. The advantage would be > capturing any potentially useful development. > > Anyway, this all is just suggestion. I would not insist on any > ------------------------------------------------------------------------------ Special Offer -- Download ArcSight Logger for FREE! Finally, a world-class log management solution at an even better price-free! And you'll get a free "Love Thy Logs" t-shirt when you download Logger. Secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsisghtdev2dev _______________________________________________ Jsynthlib-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jsynthlib-devel
