From: Suraj Kurapati Date: 2012-02-08T15:24:39+09:00 Subject: Re: Tork 18.0.0 Whoops, sorry for the late response folks. (Although I enabled notifications for this thread on RubyForum, I didn't receive any!) Nikolai Weibull wrote in post #1044504: > On Tue, Feb 7, 2012 at 10:11, Ryan Davis wrote: >>>> I'm just following RubyGems' Rational Versioning Policy: >>>> http://docs.rubygems.org/read/chapter/7 >>> >>> But perhaps you could rationalize your release cycles. > >> Suraj writes open source software and is free to do so in any way >> he wants. Technically, I agree with Ryan; see my rationale towards the end. > I felt that Suraj is making it very hard to use his software, as > it’s constantly changing and its thus nearly impossible to gain > any of the benefits that come with updates. Do you find my release notes (and ruby-talk announcements thereof) lacking? How might I change them to better convey the benefits? > you could make it a lot easier for your users to use your software > if you didn’t make, what I would consider, minor changes to > external interfaces, so easily. As a perfectionist, it's hard for me to not make such changes. :) I feel that even the smallest details in a system contribute to the overall user experience, so it's important for me to get it right. Unfortunately, I do this by iterating (experiment and reflect) so, as a consumer, you may rightfully feel annoyed by the process. It just comes with the territory, I suppose; one trade-off among many. > And if you do, collect more of them between mayor releases so that > your users don’t have to look through a change log every week to > get up to speed with the latest release. Please consider this > comment as constructive criticism. Understood. I thought "release early, release often" was the modus operandi of open source software developers, and acted accordingly. In my view, consumers of libraries and tools distributed as RubyGems are insulated from the ceaseless churn of releases and version bumps by Bundler and friends, or even ye olde gem(name, constraint) calls. Since you must *actively* choose to upgrade to a new version, it should be reasonable for me to assume that you would check the release notes for breaking changes (which are indicated by a major version number bump, by the way) and update your usage accordingly. Cheers. -- Posted via http://www.ruby-forum.com/.