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. ------------------------------- 2.4 - middle of January, 2011 -------- 4 months ------------- 2.3.2 - September 20, 2010 -------- 4 months ------------- 2.3.1 - May 31, 2010 ------- 2,5 month ------------- 2.3.0 - March 15, 2010 -------- 2 months ------------- 2.2.2 - January 11, 2010 -------- 2 months ------------- 2.2.1 - November 16, 2009 ------------------------------- -- Modestas Vainius <modes...@vainius.eu>
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Amarok-devel mailing list Amarok-devel@kde.org https://mail.kde.org/mailman/listinfo/amarok-devel
