[rspec-users] major release required?
wilkerlucio at gmail.com
Tue Jan 18 09:39:29 EST 2011
I mean since it's an acceptable exception, since the core parts of RSpec
will still same, and autotest is somekind a "plus". Generating an major
change, will make people think that RSpec was changed, with a lot of new
features and etc... And it's not the case, in current case generate a major
change for 3.0 will make a lot of confusion for users. WDYT?
+55 81 82556600
On Tue, Jan 18, 2011 at 11:15 AM, David Chelimsky <dchelimsky at gmail.com>wrote:
> Hi all,
> Since the release of rspec-2.0, I've been following Rubygems' rational
> versioning  as closely as possible. Patch releases (2.4.x) have only had
> bug fixes, and minor releases (2.x.0) have had new features, but no
> (intentionally) backward incompatible changes, which should require a major
> (3.0) release.
> The autotest extension in rspec-2.0 prefixes the command it generates with
> 'bundle exec' if it sees a 'Gemfile' in the project root directory. It turns
> out that this is not universally helpful, so there was a request to have an
> It also turns out that autotest has a bundler plugin that prefixes the
> command with 'bundle exec'. To use an autotest plugin, you just require it
> in a .autotest file in the project root. In this case:
> require 'autotest/bundler'
> I think the right thing to do is to rely on the autotest plugin, but I also
> think that this would require a 3.0 release, which feels a bit grand for
> this situation. My question to you is: do you think this warrants a major
> (3.0) release, or would it be an acceptable exception to the rule (assuming
> proper fanfare and documentation)?
>  http://docs.rubygems.org/read/chapter/7
> rspec-users mailing list
> rspec-users at rubyforge.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rspec-users