Hi,
Some of you may be wondering who I am. I'm Ketan from ThoughtWorks and
one of the newest committers to ccrb. I've recently been doing some work
to run ccrb as a jar (java -jar ccrb.jar) as a simple way to distribute
ccrb. This is still work in progress. Later worked on fixing the build
to make it go green
<http://cruisecontrolrb.thoughtworks.com/builds/CruiseControl/bcc1d7267c145420606bce26006579ba3b17b0a7>.
So far here's what's been done so far(sorry, if this sounds like a
repeat from previous conversations):
* A brand new ccrb machine - we scrapped the existing machine that was
running an ancient OS and software which we could not figure out how it
was setup(thanks @AjeyGore and Ranjib Dey from ThoughtWorks
Infrastructure Support team)
* This has the latest version of ccrb deployed on it(rev bcc1d7).
* Get builder to work for ccrb. There was some work needed to make
builder to work with rvm.
* Fix documentation generation - this was broken because of an api
change between rails 2.x and 3.0.
Next steps:
===========
I feel the next steps should be to ensure that we are able to cut out a
release(the last one was in mid 2009 - 2 years ago). To that effect I'd
like to propose the following, and gather some consensus around the next
steps.
This is fairly aggressive with the goal being able to cut a new release
without having to stop the line for developing new features. Feel free
to add anything that you feel should go into this list. These dates are
just tentative in nature, we can be a lot aggressive if we feel we're up
for it :)
* 1.5 beta end of next week(17th June)
Cut out a branch for 1.5 work. No new features land on this branch,
anything new goes to the master branch to avoid regressions.
* 1.5RC week after(24th June)
Monitor any feedback around potential bugs that crop up and get them
fixed. Cherry pick everything to master if needed.
* 1.5 week after(1st July)
Cut out a final release. Cherry pick everything to master if needed.
Just my 2 cents. Curious to hear from everyone else.
--
Ketan
http://ketan.padegaonkar.name | http://eclipse.org/swtbot
_______________________________________________
Cruisecontrolrb-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
