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

Jeff Mitchell mitchell at kde.org
Sun Sep 27 16:02:51 CEST 2009


Nikolaj Hald Nielsen wrote:
>> Sounds good to me. But I am leaning towards 1,5 monthly releases to
>> get in enough fixes to really make it worth updating.
>> So we would have 2 weeks for string changes and small new features and
>> 4 weeks fixing bugs.
> 
> I can live with that, as long as we set the dates well in advance and
> are really though on enforcing them! :-)
> 
> Imagine actually having a release plan that goes more than a single
> release into the future... what a radical idea! :-)

Yeah, I like this idea.

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  :-)

--Jeff

-------------- 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/f1f1bd51/attachment.sig 


More information about the Amarok-devel mailing list