Closed nashby closed 12 years ago
Absolutely. I'll push out a new version this weekend. :)
Sorry @nashby this completely slipped my mind last weekend. I want to get out a new version of this. I'm currently merging in pull requests as we speak. But I think I'm going to release next weekend instead. I want to give a heads up to @jeffkreeftmeijer and @martinciu to make sure it doesn't break the fuubar gems.
I'm also going to fix the versioning in this next release. The current version of ruby-progressbar should be 0.10.0
and not 0.0.10
. The next version of the gem will be 0.11.0
.
Can everyone checkout the release/v0.11.0
branch and let me know if everything seems to be working?
Again, I apologize for not being more on top of the pull requests and promise to be better about it. I've had v1.0 ready for about a year now and just haven't pushed it out. I'm preparing it and I'll have it on the development
branch later today.
BTW, v1.0 has a full test suite so there will be much less of a need for beta testing before pushing out post-v1.0 releases.
@jfelchner I can confirm that 0.11.0 works with fuubar-cucumber
(I'll change ruby-progressbar dependency after release)
As promised. Check out the README for all the new goodness: https://github.com/jfelchner/ruby-progressbar/tree/development
@jeffkreeftmeijer @nashby I just added a deprecation module which should offer very thorough (but not 100%) backward compatibility for the current versions of fuubar and fuubar-cucumber (albeit with a few deprecation warnings).
Other than the warnings, it should now be a drop-in replacement and you can update the various deprecated usages at your leisure.
After the 1.0 release, if I can get around to it, I'll make the changes myself but I can't promise anything.
The only thing left that I know of is to backport the Timecop/Delorean fix.
Please give it a try and let me know if you find any bugs.
@nashby ruby-progressbar v0.11.0 has been pushed to Rubygems
I've also created a release branch for v1.0.0
Guys, thanks for the heads-up. Right now, fuubar is locked to ~> 0.0.10
so it won't accidentally start using your new 0.11 version. I think I'll wait for 1.0 (or would that mean I'm missing out on something?). :)
@jeffkreeftmeijer you are missing a bugfix for time mocking (#8) :)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Hi, @jfelchner! Is it possible to release a new version of gem? We have some problems with Delorean gem here https://github.com/martinciu/fuubar-cucumber/issues/18 so it would be awesome to have a
ruby-progressbar
gem from rubygems with https://github.com/jfelchner/ruby-progressbar/pull/9 this fix. Thank you!