We’ve all seen this warning:
/Library/Ruby/Gems/1.8/gems/rake-0.8.3/lib/rake/gempackagetask.rb:13:Warning: Gem::manage_gems is deprecated and will be removed on or after March 2009.[/sourcecode]
Rake is using a deprecated API from RubyGems. Jim knows about the problem, we just need to get him to release a new version of Rake.
In order to get Jim to release a new version of Rake, I have decided to start a letter writing campaign:
If you would like to help get a new version of Rake released, I encourage you to send a letter to Jim, thanking him for his hard work on Rake, and asking him kindly to release the new "warning free" version.
Send your letters here:
Rake c/o Jim Weirich EdgeCase 1130 Congress Ave Cincinnati, OH 45246
Together we can get Jim to release a new version of Rake. Together we can build a "warning free" future for our children.
Not sure this will work. Jim works out of our Cincy office and won’t likely see all of the wonderful notes.
EdgeCase
1130 Congress Ave
Cincinnati, OH 45246
Thanks! I’ve updated the address
But please, feel free to send them up to the Columbus office anyway! They like them in triplicate …
The first batch will be going to Columbus. I will persuade (twist arms) people next week and have them sent to Cincinnati.
Sharing is cool. We’ll have a stack up here to parcel out to him on his visits.
Can we, perhaps, contribute with code too? What needs to be done, code-wise, to get a new version of Rake out the door?
Uh… you could just fork it from http://github.com/jimweirich/rake and fix it yourself – but where is the fun in that?
It is already fixed. Jim just needs to release it.
My plan is to have a release polished up and ready to go by the time the first postcard reaches me. The card that reaches me gets a mention in the release notes.
Release management is one of the things I hate most about maintaining a library. Surely there’s a way to make this less painful? I know there are libs for pushing the code to RubyForge, but that’s the easiest of a tedious process: there’s testing your gem to make sure you didn’t do something stupid in the build process, and there are the release notes to write, and announcements to draft for blog and mailing list(s)… This process alone is easily more than half of what keeps me from releasing updates to code, sadly. Does anyone have any solutions for this?
Jamis, Hoe does all of this for you, provided you maintain the History.txt while you work. Everything else is automatically generated for you.
Thanks Eric. I actually did know that, and now I feel stupid.
I kept meaning to investigate those options. Now I guess I really will!
You could just gem install jimweirich-rake from github
That is not the same as an official release.
I’m going to help you guys who obviously don’t get it:
A release is when you get to type
gem install rakeand it Just Works.gem install anyusername-somegemname --source http://gems.github.com/is not a release. It is a way to get a peek at the status of a gem that is in development.HTH HAND
why not replace rake with thor?
Aaron,
Not only that get fixed, but there are issues with Kernel::system() and Windows fixed in forks that got merged in 1.9 Ruby and are needed for 1.8
@Yossef: A release as you put it requires a benevolent dictator. Which is kind of a pain point.
Installing a gem from github is not equal to what’s in development there.
@Yossef: Uh, no. I stopped bothering with RubyForge ages ago, it’s a pain (wtf, written-in-PHP?) to deal with.
GitHub gems forever! Or, better yet, let’s try this new-fangled “coral” thing, eh?
@elliottcable I’m sure Tom is open to patches.