I agree that new features should probably be limited to trunk, mainly to keep things consistent. If we ever separate the JBI components from the core framework releases this won't be a problem.
Chris On Fri, Feb 29, 2008 at 8:26 AM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > I've no clear idea if we should remove it or keep it in the branch. > This is a bit of a edge case as there is really no chances to introduce > bugs on existing components. I think we need to reach a consensus > here, so that we can reach some kind of policy around that. > > My personal opinion would be to only include it in trunk ... > > .. and don't be sorry, there's no problems, mainly because we have > never really discussed that. > > On Fri, Feb 29, 2008 at 4:17 PM, Lars Heinemann > <[EMAIL PROTECTED]> wrote: > > Guillaume, > > > > it's good to hear a clear statement here from you. > > > > I just thought that it's not a bad thing to add the component to the > > 3.2 branch as well as to the trunk. But if we only want to enhance the > trunk > > with new features / components I am also fine with that. > > So if I caused trouble with my commit then I am sorry about it. > > We can also talk about removing it from the 3.2 branch. > > > > Regards, > > Lars > > > > > > Am Freitag, 29. Februar 2008 14:55:38 schrieb Guillaume Nodet: > > > > > > > We've never actually decided how we want to manage our branches, but > my > > > thoughts were that the branches would not include major new features, > only > > > bug fixes and small enhancements. > > > I've just realized that we have added at least a brand new component > in the > > > branch, and I'm wondering if this is really a good thing ... > > > Thoughts ? > > > > > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ >
