On 03/13/2011 08:59 AM, Robert Vehse wrote: > How can we make Trunk more stable, how can we get closer to a release of > code that has been in development for 1,5 years? Unless we find a dozen > or so interested and competent developers somewhere I believe the only > to get there is announcing a string-freeze (at least that's how it > "works" for Pidgin and rekkanoryo).
Our string freezes don't really get anyone interested in doing anything. I just arbitrarily pick a date and basically say "get your crap in order before then" (yes, it's worded a bit nicer, but that's the gist of it). As long as it compiles, I release it. I don't care if functionality is broken or not--it's not my code that broke it. I don't even care if translations don't get in because the translators missed my deadlines. Yes, I know this sounds like I'm uncaring/insensitive and that libpurple is perpetually in beta. The truth of the matter is that both statements are more true than not. Our "stability" is really just API stability because we haven't broken backwards compatibility since 2007, and my "caring" is just that I want to see fewer open tickets on trac. John
signature.asc
Description: OpenPGP digital signature
