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

List:       amarok-devel
Subject:    Re: tagging 2.4 in a week
From:       Mark Kretschmann <kretschmann () kde ! org>
Date:       2011-01-08 6:39:28
Message-ID: AANLkTi=_=YHDNwOz=qdqnd6FjeDpAZijr4o89e92V+4i () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jan 7, 2011 at 7:01 PM, Modestas Vainius <modestas@vainius.eu> wrote:
> Hello,
>
> On penktadienis 07 Sausis 2011 10:39:22 Mark Kretschmann wrote:
>> Yes, and no. What we should do is taking them seriously, and look over
>> the list for *really* serious bugs. That's basically the main purpose.
>>
>> On the other hand, it makes no sense to postpone a release for fixing
>> all of them. That's because of "Release Early, Release Often." It's
>> not uncommon that we gain new contributors right after a big release,
>> who might just help us with fixing these issues.
>
> FWIW, I don't think that amarok follows "Release Early, Release Often."
> philosophy [1] at the moment. Sure, those bugs might get fixed after "big
> release" but since you never do point/patch releases, users can only take
> "upgrade to git" suggestions which are by no means optimal.
>
> P.S. I'm speaking in general, not about current list of release_blocker bugs.
>
> [1] The recent trend shows a tendency of slow down. If those bugs are really
> serious, 4 months is a too long wait for serious fixes.

Well, our release schedule is the result of many factors combined.
Sometimes we decide to take a little more time, especially with big
releases like 2.4.

Also, many of us have been crazy busy over the holiday season, so we
extended the schedule a bit. Nothing dramatic, but simply our way of
working :)

-- 
Mark Kretschmann
Amarok Developer, CEO of Kretschmann Software Consulting
Fellow of the Free Software Foundation Europe
http://amarok.kde.org - http://fsfe.org - http://kde.org
_______________________________________________
Amarok-devel mailing list
Amarok-devel@kde.org
https://mail.kde.org/mailman/listinfo/amarok-devel
[prev in list] [next in list] [prev in thread] [next in thread]