On Dec 19, 2011, at 4:39 PM, Luis Lavena wrote: > On Mon, Dec 19, 2011 at 9:36 PM, Erik Hollensbe <e...@hollensbe.org> wrote: >> A lot of people in the real world(™) still depend on 1.8.7. As much as it >> sucks, I can't see how this would go well for the rubygems project. >> >> Maybe a spelled out deprecation roadmap would be a better way of saying >> "hey, 1.8.7 users, get your shit together". >> > > Yes, I understand that, however it make things a bit more complicated > when RubyGems is merged into Ruby itself and we need to keep track of > different codebase, because simply for Ruby-Core, 1.8.7 is dead.
Oh, I'm not disagreeing with you regarding the concerns; I just think that communicating the plan is just as important as carrying out. That might mean a later point of removed 1.8.7 support to give people enough time to react appropriately. I guess what I'm envisioning is a bunch of big changes to rubygems and a large portion of the user base not being able to work with the changes (be they to gem/spec formats, etc) because they're on a previously well-supported version of ruby. Communicating "we're doing this in 2.1" for example gives plenty of time for the invested users to say, "ok, we really need to get off 1.8.7 now". Anyhow just $0.02, I'll stay out of it from here on out. :) -Erik _______________________________________________ RubyGems-Developers mailing list http://rubyforge.org/projects/rubygems RubyGems-Developers@rubyforge.org http://rubyforge.org/mailman/listinfo/rubygems-developers
