> Just created the Slide 2.0 release branch called > > SLIDE_2_0_RELEASE_BRANCH > > It will be valid for all 2.0 releases ranging from beta > (2.0beta) over > release candidate (2.0rc) to final (2.0) and then also maintenance > (2.0.x) releases. It will cease to be valid as soon as there is a 2.1 > release branch containing the new features. > > *IMPORTANT* > > For bugfixing and maintenance please check out this branch and make > associated changes to this branch *only*. Otherwise merging > will be very > hard and error-prone.
So, bug fixes DONT go into HEAD, is that right? > New features and commits associated to them should still go into the > HEAD and will *never ever* be merged into the 2.0 release branch. > > This means branching will only go in one direction: You mean *merging* will only go in one direction, right? > SLIDE_2_0_RELEASE_BRANCH -> HEAD > > To get things started I will volunteer to merge branches on a regular > basis for next one or two weeks. > > As for the testsuite, I guess it will be OK to go on > maintaining it in > the HEAD, right? OK, that's fine. > If I failed to make myself quite clear, please tell me so and ask! > > Cheers :) > > Oliver > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
