On Thursday, September 20, 2012 12:45:05 Knoll Lars wrote: > Sinan will get a release team organised that helps with taking care of these > different aspects. Coordination and further communication will happen on > the releasing mailing list and the #qt-releases IRC channel, so please > subscribe there if you have an interest in helping with the release process > itself.
I'm interested in knowing what is the effective way to track release blockers for a release? There are still open blocker and critical bugs for the beta 1 release: https://bugreports.qt- project.org/secure/IssueNavigator.jspa?mode=hide&requestId=13380 So, I don't think that's where the one with the big release button to push is looking. In particular, I re-opened https://bugreports.qt-project.org/browse/QTBUG-26860 and no-one said a word about it. It's also not clear to me whether anyone is processing the package testing emails that come in, and making sure bugs are filed for new issues? Thanks, -- Stephen Kelly <[email protected]> | Software Engineer KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company www.kdab.com || Germany +49-30-521325470 || Sweden (HQ) +46-563-540090 KDAB - Qt Experts - Platform-Independent Software Solutions ** Qt Developer Conference: http://qtconference.kdab.com/ **
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Releasing mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/releasing
