On Fri, Jul 12, 2013 at 10:10 PM, James Turnbull <ja...@puppetlabs.com>wrote:
> > If it was a huge change shouldn't it be semantically versioned and up'ed > to 1.x.x? > Hopefully hunner will reply directly himself rather than me putting words in his mouth, but I believe our intent was that the first 1.0.0 would have a stable API and I think that was why it's still considered a 0. release. I think he wanted to do a few more things in terms of the parameters before calling it a 1.0. The way SemVer defines this is: Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable. Version 1.0.0 defines the public API. The way in which the version number is incremented after this release is dependent on this public API and how it changes. Admittedly the apache module is a unique snowflake as people use it in production but we've never really had any clear concept of what a real 1.0 release would be and what we'd be able to commit to making sensible releases around. -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-dev+unsubscr...@googlegroups.com. To post to this group, send email to puppet-dev@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
