On 18 okt 2010, at 14:23, Armin Ronacher wrote: > Hi everybody, > > This will also finally make it possible to decide on the future of Werkzeug > because I will maintain with the 0.7 release a proper maintenance branch > where bugfixes go and an experimental branch that should clean up code for > 1.0 and remove a few features that really should be in their own package.
Personally I think http://semver.org/ describes pretty accurately what 0.x means, quote: > 6. Version 1.0.0 defines the public API. The way in which the version number > is incremented is now dependent on this public API and how it changes. ... > Doesn't this discourage rapid development and fast iteration? > > Major version zero is all about rapid development. If you're changing the API > every day you should either still be in version 0.x.x or on a separate > development branch working on the next major version. Also a point worth noting that I'm sure you agree with this: > How do I know when to release 1.0.0? > > If your software is being used in production, it should probably already be > 1.0.0. If you have a stable API on which users have come to depend, you > should be 1.0.0. If you're worrying a lot about backwards compatibility, you > should probably already be 1.0.0. You should've released 1.0.0 a long time ago. :D IOW: What you suggest sounds like a sane path of action, and I drew this ASCII graph: werkzeug -> 0.5 -- 0.6 ------ 1.0 -- 1.1 -- 1.2 -- ... \-- 0.7 All in all this whole e-mail is a prolonged "+1", so I'll cut it short -Ludvig -- You received this message because you are subscribed to the Google Groups "pocoo-libs" 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/pocoo-libs?hl=en.
