Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide



Rockbox mail archive

Subject: Re: Rockbox development model

Re: Rockbox development model

From: Jonas Häggqvist <rasher_at_rasher.dk>
Date: Fri, 10 Aug 2007 15:27:07 +0200

pondlife wrote:
>>> 4-6. Everyone is encouraged to fix bugs in the rel-3.0 branch.
>
> Maybe this should be in the trunk - i.e. bug fix week or freeze. That saves
> us having to fix said bugs in both trunk and 3.0.

I actually did this for a reason, but on second thoughts I think you're
right. My reason for doing the bugfixing in the release branch was to avoid
ever having freezes in trunk, which has been shown to frustrate people, and
possibly be counter-productive. On the other hand, having to fix bugs in two
branches is probably not worth it. A freeze in trunk prior to branching
sounds like the better solution.

>>> 7. ...After this (or possibly during 4-6), new features should get into
> trunk...
>
> If you do 4-6 as per your plan, then new features must be allowed into trunk
> immediately (i.e. no freeze).
> If you do 4-6 as I suggest above, then we only allow new features at 7.

My proposal was a sort of "soft freeze" of trunk during the pre-release
bugfixing, where people were simply encouraged to work on the release-branch
rather than working on new features for trunk, but now that I think about
it, I agree that the overhead of doing bugfixes twice is not worth it.

-- 
Jonas Häggqvist
rasher(at)rasher(dot)dk
Received on 2007-08-10

Page was last modified "Jan 10 2012" The Rockbox Crew
aaa