On Sun, Feb 10, 2013 at 3:00 PM, Franklin Webber <franklin.web...@gmail.com>wrote:
> Will the gems that are dependent on Haml now just break from the "breaking > changes" versus breaking from a version number difference? > Thanks for the feedback. The breaking changes coming in 3.2 have been public knowledge for many months. Changing the major version to 4 is in and of itself another potential breaking change because it could break version checking code. I don't think springing that on people with less than 2 days notice is a good idea. We've set the expectation now for many months that the next version will be 3.2 and not 4.0, and I think it's best to stick with that. I'm very open to switching to semantic versioning for the next release. However I am not going to do it willy-nilly two days before a release without having the time to carefully think through how it will affect the project. -- You received this message because you are subscribed to the Google Groups "Haml" group. To unsubscribe from this group and stop receiving emails from it, send an email to haml+unsubscr...@googlegroups.com. To post to this group, send email to haml@googlegroups.com. Visit this group at http://groups.google.com/group/haml?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
