ALERT: KDElibs (at least) 4.8.4 is actually 4.8.80+

Albert Astals Cid aacid at
Sun Jun 10 13:27:55 UTC 2012

El Dissabte, 9 de juny de 2012, a les 13:53:06, Wulf C. Krueger va escriure:
> >> I see basically nothing *systematically* being done about it.
> > 
> > Even i don't agree they are a mess, I'll bite and ask if you have
> > any suggestion.
> Well, they were mostly in the email I linked you to but here's the gist:
> - - Before announcing the tarballs, build the whole thing at least once.

We do that, that's why we have a week before the release where packagers get 
access to pre-release tarballs.

For example all the mails you are seeing about the beta2 tarballs are over 
tarballs that are not public not announced yet, so you can't say we don't 
build them, we do build them, again you are just having a different perception 
of the reality because we operate in the open instead of behind closed doors.


> - - Freeze earlier and use the time to do more (systematic!) developer
> testing.
> - - Improve the test cases. They *do* help in catching bugs.
> - - Implement more trivial code screening (e. g. for bogus versions).
> - - Re-think the release engineering process. (No actual, hard
> suggestions here.)
> A more radical approach and one I'm personally greatly in favour of:
> Get rid of time-based release cycles but switch to content-based
> releases. Instead of rushing things towards the end of a time-based
> release cycle, describe features/bugs/any kind of content you want to
> see done before another release.
> Whatever you guys decide to do (or not do), I'd really appreciate it
> if you thought about your process and its basics again.
> Even if you think the releases are not a "mess" there must be a reason
> some people (some of them being "seasoned KDE veterans" ;-) )
> *perceive* them to be one.
> - --
> Best regards, Wulf
> Version: GnuPG v2.0.19 (GNU/Linux)
> Comment: Using GnuPG with Mozilla -
> RdUAoNJgGjp4OCSQIRm1cM+KFanvtjo6
> =czvg
> _______________________________________________
> release-team mailing list
> release-team at

More information about the release-team mailing list