about summary refs log tree commit homepage
path: root/Rakefile
DateCommit message (Collapse)
2011-01-21doc: git.bogomips.org => bogomips.org
bogomips.org is slimming down and losing URL weight :)
2010-12-29Rakefile: fix fm_update task
Oops
2010-12-24doc: switch documentation generation to wrongdoc
It is a common base so we can share documentation tasks more easily with Unicorn and it ensures our RDoc no longer has JavaScript in it!
2010-10-26Rakefile: updates for prereleases
We do prereleases, now.
2010-08-03maint: publish Rubyforge news on release
I keep forgetting, so I'll force it on myself.
2010-06-04tests: cleanup isolate usage
We don't need tmp/ in our top level directory
2010-06-04Rakefile: explain ourselves when Isolating
Yes there's a reason for everything we do :>
2010-06-03depend on Isolate ~> 2.0.2 for development
It's useful given all the Gems we support but don't have hard installation dependencies on.
2010-05-14update isolate config for Isolate 2.0.0
2010-04-19use the excellent `isolate' gem for dev
It should make life easier when dealing with and testing complex dependencies, especially ones like Cramp which depend on prerelease versions of gems.
2010-02-01Rakefile: autoload Gem
easier to manage for cases where rake isn't a gem itself
2009-12-13Rakefile: fix fm_update task
2009-12-13Rakefile: resync with Unicorn
* cleanup NEWS.atom.xml feed * add freshmeat update task
2009-11-15Rakefile: add raa_update task
2009-10-20add news bodies to site NEWS.atom.xml
While we're at it, remove trailing whitespace for author names, too.
2009-10-05summary: s/slow apps/sleepy apps/g
I think "sleepy" is a better term than "slow" here. "slow" can mean apps that are CPU/memory bandwidth-bound, and Rainbows! sucks at those.
2009-10-05Fix NEWS generation on single-paragraph tag messages
commit 2643f9c34a4fc63ab9533d851a564be93dcc8bdb from Unicorn
2009-10-05Rakefile: add publish_news target
2009-10-05huge documentation revamp
2009-10-04doc updates; use "Rainbows!", not "Rainbows"
Also add notes about development things and the configuration language which uses "Rainbows!". Calling ourselves "Rainbows!" will help us be taken even more seriously than if the project were just called "Rainbows"
2009-10-02initial revision
No tests yet, but the old "gossamer" and "rainbows" branches seem to be basically working.