- From: Erik Hollensbe <
>
- To:
- Subject: [chef-dev] chef 0.9 patches to support new features of rubygems 1.8.x ?
- Date: Mon, 21 Nov 2011 09:07:10 -0800
Just subscribed to these lists -- I apologize if I have the incorrect list...
I was told by one of your comrades in #chef that the lists would be the best
place to ask this question.
We're in the process of upgrading our rails stacks to support rubygems 1.8.x
-- but we're still on 0.9 chef which is still using the now-deprecated and
soon-to-be-dead SourceIndex API. What we'd like to do is submit patches to
resolve the outstanding issues in a portable way (so they'll still be
compatible with 1.3+, but not raise the warning with 1.8.x), but obviously
this would merit a new release.
Judging from our use of opscode hosted chef, you guys haven't completely
EOL'd chef 0.9 yet; would these patches be something you'd be willing to
consider? Our team has two rubygems committers on it, so I think we'll be
able to satisfy any concerns you might have.
We understand there are contributor agreements involved, this is more about
pushing for a new release and getting permission for the patches, etc.
Thanks!
-Erik
- [chef-dev] chef 0.9 patches to support new features of rubygems 1.8.x ?, Erik Hollensbe, 11/21/2011
Archive powered by MHonArc 2.6.16.