[haiku-development] Re: Haiku R1 Feature Freeze - Jan 31st, 2017 branch!

  • From: Sean Collins <smc.collins@xxxxxxxxxxx>
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Sun, 04 Dec 2016 16:01:25 -0500

waddlesplash wrote:

On Sun, Dec 4, 2016 at 12:54 PM, kallisti5 <kallisti5@xxxxxxxxxxx> wrote:
When the branch occurs, no new features will be accepted into the R1 release
branch.

We currently plan on the R1 branch running through R1B1,R1B2+ and release
candidates.

Once again, branching R1 off master and then letting master move
towards R2 is a *bad idea*. We aren't getting paid to do this, so if
there isn't a roadblock in the way to force people to work towards R1,
very few people will do it. Plus, cherry picking stuff is super time
consuming.

Only branch R1B1 just before release; otherwise just feature-freeze
master so everyone is forced to work on bugfixes and not $pet_feature.

-waddlesplash


I do not believe that you can just feature freeze git ? so that freeze would have to be voluntary.

Sean

Other related posts: