> But that's getting ahead of ourselves. We need to keep our eyes > focused on 1.0, which is in feature freeze. So, new features isn't > our problem it's just the number of people who are working on > documenting the existing features.
Now those are the words I've been hoping to hear! The same thing happened before the massive Csound5 rewrite. Feature freezes are not fun, and are discouraging to people experimenting with the code, and inevitably generate some friction. But two years later, the result was massively worth it. At some point it becomes necessary. If I know that we have a code freeze on a stable plan in place, that dramatically increases my motivation to do things like help out with tutorials and what not because I know the time won't be wasted when the api I'm still just figuring out gets changed again. Thanks. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
