[haiku-development] Re: R1/A3: a thought about the release cycle.
- From: "Adrien Destugues" <adestugu@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 02 Nov 2010 19:10:20 +0100
> Following up on the R1/A3 talks [1],
> one of the major hurdles seems to be the lack of a release branch
> manager.
>
> Would it be possible to enforce a very strict merging-to-branch
> policy?
>
> This should greatly reduce the workload of the branch manager. As the
> branch
> should be seeing less commits, it should make it easier to perform QA
> and spot any regressions.
I believe the 'alpha' selection should not be made on commits, but on
tickets in trac. If a commit fixes a ticket attached to the alpha
milestone, it goes in the branch. If not, it stays out.
This way, the merging becomes an easier task, with less review to do,
as most of the decision work is done beforehand.
--
Adrien / PulkoMandy.
Other related posts:
