Two announcements:
Skip all this blah blah and them both with one simple command:
rubyforge 0.3.0
I'm proud to announce that codeforpeople's rubyforge 0.3.0 has been released! This release further refines rubyforge's abilities, adding news posting and finally adding multiple file releases!
We still have a lot of plans for this library. Next on the list is to be able interact with tracker, error checking, and a much more powerful and mostly automatic configuration system.
- 0.3.0 / 2006-10-03:
- Added more debugging output if $DEBUG
- Added news posting.
- Added multiple file release to addrelease (uses addfile for extras).
- addrelease now returns releaseid
- Fixed config scraper to include '-' in names.
hoe 1.0.5
Hoe has become a monster I'm falling for. Tiny, simple, nicely constrained, yet rather powerful.
- Doco cleanup.
- Removed Manifest.txt from rdoc and added title.
- Added changeset support.
- Added spec_extras for easy gemspec attribute setting.
- Added release_notes, changeset setting for releases.
- Added paragraphs_of utility method.
- Added email and rubyforge news announcement tasks.
- Url attribute may now be an array of urls.

Are you hoes developing similar functionality to metaproject ;-) ? (http://rubyforge.org/projects/xforge/)
It allows you to upload multi-file rubyforge releases and news - all from within Rake
We looked at metaproject and it was deemed overkill. Case in point:
./lib/meta_project/project/xforge/session.rb: def release(release_name, filenames, release_notes = "", release_changes = "", package_name = nil, preformatted = true, processor = Processor::ANY)or simply:
vs (hoe and rubyforge):
Yes, metaproject is overengineered, I admit. And not very elegant - it was my first crack at HTTP and screen scraping. It does the job, but now I am defeated. :-D
I like what you've done with hoe and rubyforge.
I think I'll switch to it myself!