Proposal: A series of time based releases for 2.2.x

[Jeff Mitchell]

Téo Mrnjavac wrote:
> On Sun, Sep 27, 2009 at 5:00 PM, Nikolaj Hald Nielsen
> <nhnfreespirit at gmail.com> wrote:
>>> I think some math was wrong though -- in a four-week cycle there'd be
>>> two weeks of bug fixes and two weeks of translation, and for 1.5 months
>>> there'd be two weeks of bug fixes and four weeks of translation? Seems
>>> to me it should be 4+2 and not 2+4  :-)
>> No, I think 2 for features/strings and 4 for bug-fixing is about right
>> if our focus is on stability. Besides, people will hack away in git
>> anyway.
>>
> It's not like you can't focus on stability during the non-frozen time
> period. An excessively long string freeze can actually get in the way
> of fixing some issues. Why not just make it 3+3?

Right, that was kind of my point. I don't see the utility of having a
string freeze longer than necessary for the translators. After all,
clarifying or enhancing a string *is* a bugfix  :-)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/amarok-devel/attachments/20090927/301bf59c/attachment.sig