On 23 nov, 15:01, Mislav Marohnić <[email protected]> wrote: > > I have a problem with Haml versioning. Why are such major features and some > deprecations added to a minor release? If I wrote some code and deployed it > with Haml 2.2.13, keeping the version constraint as "~> 2.2.13", I don't > expect it to suddenly spew out deprecation notices if I update to a newer > 2.2.x version.
Painful experience navigating the Ruby ecosystem has taught me to never specify that kind of ">" version requirement if I can avoid it, instead always requiring specific, exact versions if possible. (This isn't something that's unique to Haml; it's a good idea with pretty much any gem as far as I'm concerned.) Cheers, Wincent -- You received this message because you are subscribed to the Google Groups "Haml" 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/haml?hl=en.
