[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[mylyn-dev] development process
|
We are still in the process of figuring out the best strategy for the
maintenance branch. On today's call we agreed to the following:
- set the milestone to 2.3 for each bug that is fixed on the maintenance
branch
- add the [m2.3.x] (x == maintenance revision) tag to the title of the bug to
mark fixes that go into a particular release
- commit the fix to the branch as well as to head
My suggestion is that we also attach patches to the corresponding bugs for all
changes that are committed to the maintenance branch. My thinking is that it
makes it easy for other committers to review changes. It also helps to track
if a change is committed to the branch as well as to head.
It is important that we don't introduce regressions for the maintenance
branch. Less committers will work bootstrapped from the branch and weekly
builds will have less exciting changes. Meaning we are likely to get less
feedback for changes made to the branch and run at higher risk to miss
regressions.
Steffen
--
Steffen Pingel - steffenp@xxxxxx - http://steffenpingel.de
