I've branched and tagged 1.4.0 on github. I've also updated the main server with the latest cc.rb (and added rspec and all its dependencies as a demo project). I've also got a tgz out on rubyforge. I've named the file cruisecontrol-1.4.0.tgz rather than cruisecontrolrb-1.4.0 - I hope that's fine since there seems to be no way to edit a release.

Can please someone test all of this to make sure I haven't missed something? We can announce this once everything looks ok.

Chad, I'm not sure how to do the CR/LF stuff myself - Alexey, how do we do this?

Best,
Sidu.

Brian Guthrie wrote:
Just pushed all of my documentation changes. It ended up becoming a
full-on housecleaning and took considerably longer than I thought it
would but things are in better shape now. It's 2 AM in California and
I need to catch some sleep, but Sidu if you get a chance please do
push the release out. (Check release_checklist.red if you haven't seen
it yet for some helpful reminders of what needs to get done.)

I've tried to update the Team page (team.red) appropriately by looking
through the Git commit logs - please, everyone, take a look and revise
where you deem appropriate.

Brian

On Mon, Jun 29, 2009 at 10:04 AM, Brian Guthrie<[email protected]> wrote:
Not quite yet. I still need to finish up a couple of revisions, and push
what I've got.

Cheers,

Brian

On Jun 29, 2009, at 4:40 AM, "C. K. Ponnappa" <[email protected]> wrote:

So, gentlemen, it's Monday. Are we ready to branch, tag and release, or is
there anything pending?

Best,
Sidu.
_______________________________________________
Cruisecontrolrb-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
_______________________________________________
Cruisecontrolrb-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

_______________________________________________
Cruisecontrolrb-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers

Reply via email to