On Wed, Feb 16, 2011 at 8:44 AM, Ryan Davis <[email protected]> wrote: > With 1.4 our focus was on cleaning up our house and getting a long overdue > release out. > > With 1.5 our focus was on cleaning up the mess in mri 1.9. > > And 12 days from now I plan on releasing 1.6. > > I've focused on revamping dependency resolution to make it more accurate. I > just got our last failing test to pass. This probably just means that we're > missing failing tests. We need as many eyeballs on these changes as possible. >
With this new dependency resolution tests, are we considering the "use cases" of Bundler? I've tried to look at Bundler gem activation specs (or the reason bundler exist) and couldn't find a single one. Ideally would like RubyGems is a bit smarter in relation to dependency resolution, like not pulling the latest version of a gem unless needed... > Please poke at it and report any bugs you find. The easiest way to do this > would be to install from git by running setup.rb. DO NOT DO THIS if you plan > on releasing any gems between now and the actual release. Package them. Poke > at them. But don't release them. > Will merge first the fixes for test complete on Windows and will start using it daily and see what happens. > Thank you. Thanks to you for the refreshed attention to RubyGems, really appreciate it. -- Luis Lavena AREA 17 - Perfection in design is achieved not when there is nothing more to add, but rather when there is nothing more to take away. Antoine de Saint-Exupéry _______________________________________________ Rubygems-developers mailing list http://rubyforge.org/projects/rubygems [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
