[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice-devel
Subject:    Re: feature branch during freeze
From:       Thomas Zander <zander () kde ! org>
Date:       2010-09-07 16:40:53
Message-ID: 201009071840.53674.zander () kde ! org
[Download RAW message or body]

We are in feature freeze to allow people to refocus on bugfixing. And we have 
*plenty* of bugs that need fixing.
What went pretty bad in my experience last time is that we got a very strong 
split in the community; either you were on the feature branch or you were on 
the bugfixing branch. Almost nobody was compiling both.

I'm afraid the same thing will repeat itself; people will focus on new features 
and let the main-application maintainers fix the bugs to get ready for release.
We have had a lot of new features introduced and a few too many of them are 
buggy and caused regressions.
If we are serious (and I hope we still are) about getting end-user-ready then 
lets not split the community again like we did last release.

I propose we focus on writing unit tests and fixing regressions and making the 
new features shippable.

If people want to work on a new feature they naturally can, but lets not 
encourage it.


On Tuesday 7. September 2010 14.07.27 Boudewijn Rempt wrote:
> Like last time, I think it would be a good idea to allow people with
> different schedules/priorities to continue development features in a
> branch.
> 
> It worked quite well during the 2.2 freeze, with the only hickup being the
> name of the branch. I propose that we name the branch after the last place
> where a KOffice sprint was organized, so:
> 
> koffice-essen
> 
> And for the rest, the same rules we used last time should apply:
> development in the branch is open, you only need to ask for review if you
> are unsure about something, but when merging back to trunk, your patches
> need to be cleaned up and posted for review.
> 
> Currently, Casper and me are joshing about who's going to do the daily
> merge from trunk -- but we'll find a formula :-).

-- 
Thomas Zander
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]