> How about a feature freeze & release candidates & bug fixing before > releasing SHR stable? In it's current state I can't see a reason to > call it stable :/
Well, the feature freeze and release candidate are out there since December 2009 basically, because old shr-t -> shr-stable. Not the current shr-t. > Renaming unstable to testing every now and then and then renaming > testing again to stable every now and then (without allowing time for > testing to be tested & bugfixed but importing new bugs from -unstable) > doesn't seem like a very good approach to produce stable releases.. I agree, but no one picked up the task of actually maintaining a shr-stable. So, the *old* shr-Testing snapshot is going to become shr-stable. We'll have to work hard to get the current shr-testing into a good shape though, I agree. Unfortunately all those underlying architectural changes make things shakier than we whish.... :-( spaetz _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
