The roadmap says we will release M3 this week. With 194 packages not building (many of them caused by more strict implementation of FORTIFY_SOURCE it seems) I'm not really sure we can make it. Then again I prefer releasing a buggy M3 that allows testing than not releasing any milestone and not having any testing. But I won't release anything that doesn't allow testing - so we'll see.
I fully agree that a buggy milestone is better than none - but regarding something that allows testing, make sure http://bugzilla.novell.com/show_bug.cgi?id=582222 is fixed on Factory before you release anything, not being able to boot the kernel is quite bad. Also, I recently (also since gcc 4.5?) can't use much of YaST any more, esp. not the package manager, would be good to have such core things fixed to at least run reasonably when shipping a milestone. (I know how hard it is to ship something even for testing - the project I'm working on has unit tests that run and check essential features, though, which eases problem finding and solving - but then, not a distro, but a single application I'm shipping). Robert Kaiser -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org