Hi all, I'd like to apologize. I haven't been able to offer the level of support to the project that it deserves. With this in mind, I've recently asked for, and been allowed, some time by ThoughtWorks to update and improve CC.rb. Here's what's happened:
- Framework has been upgraded to Rails 3 - Along with that, there's been a lot of configuration, domain model, and test cleanup - Minor aesthetic improvements (look for more here soon) - Can add new projects using the UI - Now manages dependencies with Bundler (naturally) - Lots of old Rails JS helpers replaced with properly-written JS (framework is still Prototype) Here's what I know works: - All tests pass - Cruise command appears to function correctly - Can build stuff (which is nice) - No major routes or configuration settings have been changed (to my knowledge) Here's what I'd like to do: - Improve TW's ability to provide ongoing maintenance and support - Attempt to "do the right thing" wrt. Bundler; I'm open to feedback on the appropriate level of support to offer, keeping in mind that simplicity is key - Add support for performing push-button deploys - we've faked this on projects in the past - Allow you to group builds, providing proper first-class domain support for the difference between a project, a build, and a particular execution of a build (for me personally, high pain, high priority) - Some RJS still exists that I'd like to kill (moderate pain, low priority) - A lot could be done to improve the dashboard UX - I'd like to add support for JSON representations of most important entities (perhaps JSONP too?) - I'd like to consolidate all bugs and feature requests in the Github feature tracker and either close or fix what's already there - I'd like to find a way to distribute builds to multiple boxes without spinning up multiple instances of CC.rb (high complexity, low priority) - I haven't yet tested any of this in Windows (for me personally, low pain, low priority) Here's what I'd like to know: - Is anything in the above list worthwhile? - What are your most acute pain points? - What do you suggest for other reasonable next steps? Thanks, Brian _______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
