Rails upgrade
|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
 |
Rails upgrade
by Brian Guthrie-3
::
Rate this Message:
Hi all, A few of my colleagues and I have forked CCRB and have it running on Rails 2.3. It doesn't fully integrate Rails 2 idioms yet, but it successfully deploys on Passenger and builds itself. We've rebased with thoughtworks/master as of a couple of hours ago. As a ThoughtWorker I have access to the TW account on GitHub; would anyone object if we merged these changes in? We'd be happy to integrate it as part of a distinct Rails 2 branch if need be. http://github.com/bguthrie/cruisecontrol.rb/tree/master Thanks all, Brian _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
|||||||||||
|
|
Re: Rails upgrade
by Jeremy Lightsmith
::
Rate this Message:
In general, it sounds great to me.
My one concern is that we really, REALLY need to do a release. I know Alexey was going to, but now that he's not at TW either, who has access to http://cruisecontrolrb.thoughtworks.com? Does ccrb have a TW sponsor anymore? If we can muster some help to get the release out sooner than later, I'd hold off on the rails 2.3 upgrade until after that. If we can't, then I'd go ahead and do it now. One thing to note, the current philosophy of ccrb is to make it dependency free. So be sure when we upgrade to freeze the rails gems. Jeremy On Tue, May 19, 2009 at 7:41 PM, Brian Guthrie <bguthrie@...> wrote:
-- Jeremy Lightsmith Coaching Teams & Creating Communities 312-953-1193 http://onemanswalk.com/ (blog) http://facilitationpatterns.org/ (book in progress) http://www.linkedin.com/in/jeremylightsmith _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
|||||||||||
|
|
Re: Rails upgrade
by Jeff Xiong
::
Rate this Message:
Jeremy,
I'll check if there's nobody else handles this... On Wed, May 20, 2009 at 5:03 PM, Jeremy Lightsmith <jeremy.lightsmith@...> wrote: > In general, it sounds great to me. > > My one concern is that we really, REALLY need to do a release. I know > Alexey was going to, but now that he's not at TW either, who has access to > http://cruisecontrolrb.thoughtworks.com? Does ccrb have a TW sponsor > anymore? > > If we can muster some help to get the release out sooner than later, I'd > hold off on the rails 2.3 upgrade until after that. If we can't, then I'd > go ahead and do it now. > > One thing to note, the current philosophy of ccrb is to make it dependency > free. So be sure when we upgrade to freeze the rails gems. > > Jeremy > > On Tue, May 19, 2009 at 7:41 PM, Brian Guthrie <bguthrie@...> > wrote: >> >> Hi all, >> >> A few of my colleagues and I have forked CCRB and have it running on Rails >> 2.3. It doesn't fully integrate Rails 2 idioms yet, but it successfully >> deploys on Passenger and builds itself. We've rebased with >> thoughtworks/master as of a couple of hours ago. As a ThoughtWorker I have >> access to the TW account on GitHub; would anyone object if we merged these >> changes in? We'd be happy to integrate it as part of a distinct Rails 2 >> branch if need be. >> >> http://github.com/bguthrie/cruisecontrol.rb/tree/master >> >> Thanks all, >> >> Brian >> _______________________________________________ >> Cruisecontrolrb-developers mailing list >> Cruisecontrolrb-developers@... >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers >> > > > > -- > Jeremy Lightsmith > Coaching Teams & Creating Communities > > 312-953-1193 > http://onemanswalk.com/ (blog) > http://facilitationpatterns.org/ (book in progress) > http://www.linkedin.com/in/jeremylightsmith > > _______________________________________________ > Cruisecontrolrb-developers mailing list > Cruisecontrolrb-developers@... > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > > -- Jeff Xiong Software Journeyman - http://gigix.agilechina.net Open Source Contributor - http://fluorida.googlecode.com/ Technical Evangelist - http://www.infoq.com/cn/ _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
|||||||||||
|
|
Re: Rails upgrade
by Brian Guthrie-3
::
Rate this Message:
Alexey gave me his blessing to be the new maintainer before he left, but I haven't yet received the rubber-stamp from TW management and don't have access to the content on cruisecontrolrb.thoughtworks.com as of yet (nor do I have admin rights on the Lighthouse tracker). I think it makes sense to hold off on the Rails upgrade until after a new release has been pushed out, so I won't merge just yet. What more needs to be done in order to push the release out, just rev the site? Brian
Jeremy, I'll check if there's nobody else handles this... On Wed, May 20, 2009 at 5:03 PM, Jeremy Lightsmith <jeremy.lightsmith@...> wrote: > In general, it sounds great to me. > > My one concern is that we really, REALLY need to do a release. I know > Alexey was going to, but now that he's not at TW either, who has access to > http://cruisecontrolrb.thoughtworks.com? Does ccrb have a TW sponsor > anymore? > > If we can muster some help to get the release out sooner than later, I'd > hold off on the rails 2.3 upgrade until after that. If we can't, then I'd > go ahead and do it now. > > One thing to note, the current philosophy of ccrb is to make it dependency > free. So be sure when we upgrade to freeze the rails gems. > > Jeremy > > On Tue, May 19, 2009 at 7:41 PM, Brian Guthrie <bguthrie@...> > wrote: >> >> Hi all, >> >> A few of my colleagues and I have forked CCRB and have it running on Rails >> 2.3. It doesn't fully integrate Rails 2 idioms yet, but it successfully >> deploys on Passenger and builds itself. We've rebased with >> thoughtworks/master as of a couple of hours ago. As a ThoughtWorker I have >> access to the TW account on GitHub; would anyone object if we merged these >> changes in? We'd be happy to integrate it as part of a distinct Rails 2 >> branch if need be. >> >> http://github.com/bguthrie/cruisecontrol.rb/tree/master >> >> Thanks all, >> >> Brian >> _______________________________________________ >> Cruisecontrolrb-developers mailing list >> Cruisecontrolrb-developers@... >> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers >> > > > > -- > Jeremy Lightsmith > Coaching Teams & Creating Communities > > 312-953-1193 > http://onemanswalk.com/ (blog) > http://facilitationpatterns.org/ (book in progress) > http://www.linkedin.com/in/jeremylightsmith > > _______________________________________________ > Cruisecontrolrb-developers mailing list > Cruisecontrolrb-developers@... > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers > > -- Jeff Xiong Software Journeyman - http://gigix.agilechina.net Open Source Contributor - http://fluorida.googlecode.com/ Technical Evangelist - http://www.infoq.com/cn/ _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
|||||||||||
|
|
Re: Rails upgrade
by Chad Woolley
::
Rate this Message:
On Wed, May 20, 2009 at 5:21 AM, Brian Guthrie
<bguthrie@...> wrote: > > Alexey gave me his blessing to be the new maintainer before he left, but I > haven't yet received the rubber-stamp from TW management and don't have > access to the content on cruisecontrolrb.thoughtworks.com as of yet (nor do > I have admin rights on the Lighthouse tracker). > On Wed, May 20, 2009 at 5:03 PM, Jeremy Lightsmith > <jeremy.lightsmith@...> wrote: >> In general, it sounds great to me. >> >> My one concern is that we really, REALLY need to do a release. I know >> Alexey was going to, but now that he's not at TW either, who has access to >> http://cruisecontrolrb.thoughtworks.com? Does ccrb have a TW sponsor >> anymore? We depend heavily on CCRB at Pivotal Labs, and we have been contributing bugfixes and patches, and I also spend my free time monitoring this list and using CCRB for other projects (such as the official Rails CI server). Especially since Alexey left, the future of CCRB support from ThoughtWorks is concerning to me. Is ThoughtWorks committed to maintaining CCRB long-term? Is the release process still going to be controlled only by ThoughtWorks? For example - there's been several mentions of a badly-needed release over the past few months, but nothing has happened. I posted about the broken official CCRB CI build/server (I think it is a Ruby 1.8.7 problem, and will try to fix eventually), but I got no responses on that thread, and no apparent concern (I personally think it looks pretty bad for the official build of a CI product to be red). If CCRB is a strategic product for TW, and they want to maintain a level of control, then I'd like to see official TW representatives/sponsors responding more on this list, and driving releases, patches, website updates, managing the official CI server, etc. I already have commit access and a signed TW NDA on file, so I'm glad to help, but there's still many things I don't have permission to do. On the other hand, If TW is not going to take so much of an active long-term involvement (perhaps because of focus on other CI products), that is fine. However, if this is the case, I'd like to see everything open sourced and put under community ownership as well - such as the website, official CI server, release cycle, etc... So, I'm not trying to be negative, but the current situation seems far less than optimal, especially for a product my company and I depend on heavily, and I'm wondering what will happen going forward. Thanks, -- Chad _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
|||||||||||
|
|
Re: Rails upgrade
by Alexey Verkhovsky-2
::
Rate this Message:
On Wed, May 20, 2009 at 6:21 AM, Brian Guthrie <bguthrie@...> wrote:
Alexey gave me his blessing to be the new maintainer before he left, but I haven't yet received the rubber-stamp from TW management and don't have access to the content on cruisecontrolrb.thoughtworks.com as of yet (nor do I have admin rights on the Lighthouse tracker). Brian, I sent you the Lighthouse invite with admin rights on the account. As for the server access, all you need to do is to ask Barrow about that. TW management doesn't want to kill this project because of Cruise, it just doesn't care too much about it. So, it's up to the individual to keep it up. I must admit, I have done a terrible job of it in the last few months - being lazy, on a traveling gig, and not using the thing myself pushed that commitment well below the bar of things that get done. Sorry about that. Actually, now that I'm not stuck on planes and in airports for 20 hours a week and will be using it again (at Scribd), I will almost certainly be more active again. --Alex _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
|||||||||||
|
|
Re: Rails upgrade
by Brian Guthrie-3
::
Rate this Message:
Hi Chad, On my current project we're heavy users of CCRB and have a complex deployment environment (the same project for which Pat Farley contributed those feature suggestions in Lighthouse a few months back). It's safe to say that we, too, have been dismayed by the lack of recent love for CCRB. Railsconf and Integrity provided the impetus for me personally to get my act together and get serious about contributing fixes, improvments, and making sure it was well-maintained. I hate to see Alexey leave TW, but I'm glad to know that he'll be in a better position now to contribute, and as for myself and TW, we're not going to let CCRB go away anytime soon. It's a great piece of software and we've used it on every Rails project I've ever been on. We're committed to making sure that it keeps pace with the rest of the community from now on. Since I haven't done much work with CCRB in the past, I don't want to come on too strong; this is an open source project, and it belongs to you and Jeremy and Alexey and all of the other dedicated maintainers. But I and, I'm sure, others here have some ideas about ways we can improve the app and I'm hoping to finish up a 1.4 release and start putting together the features for a 2.0 release in the coming weeks. Does that sound like a reasonable plan? Cheers, Brian
On Wed, May 20, 2009 at 5:21 AM, Brian Guthrie <bguthrie@...> wrote: > > Alexey gave me his blessing to be the new maintainer before he left, but I > haven't yet received the rubber-stamp from TW management and don't have > access to the content on cruisecontrolrb.thoughtworks.com as of yet (nor do > I have admin rights on the Lighthouse tracker). > On Wed, May 20, 2009 at 5:03 PM, Jeremy Lightsmith > <jeremy.lightsmith@...> wrote: >> In general, it sounds great to me. >> >> My one concern is that we really, REALLY need to do a release. I know >> Alexey was going to, but now that he's not at TW either, who has access to >> http://cruisecontrolrb.thoughtworks.com? Does ccrb have a TW sponsor >> anymore? We depend heavily on CCRB at Pivotal Labs, and we have been contributing bugfixes and patches, and I also spend my free time monitoring this list and using CCRB for other projects (such as the official Rails CI server). Especially since Alexey left, the future of CCRB support from ThoughtWorks is concerning to me. Is ThoughtWorks committed to maintaining CCRB long-term? Is the release process still going to be controlled only by ThoughtWorks? For example - there's been several mentions of a badly-needed release over the past few months, but nothing has happened. I posted about the broken official CCRB CI build/server (I think it is a Ruby 1.8.7 problem, and will try to fix eventually), but I got no responses on that thread, and no apparent concern (I personally think it looks pretty bad for the official build of a CI product to be red). If CCRB is a strategic product for TW, and they want to maintain a level of control, then I'd like to see official TW representatives/sponsors responding more on this list, and driving releases, patches, website updates, managing the official CI server, etc. I already have commit access and a signed TW NDA on file, so I'm glad to help, but there's still many things I don't have permission to do. On the other hand, If TW is not going to take so much of an active long-term involvement (perhaps because of focus on other CI products), that is fine. However, if this is the case, I'd like to see everything open sourced and put under community ownership as well - such as the website, official CI server, release cycle, etc... So, I'm not trying to be negative, but the current situation seems far less than optimal, especially for a product my company and I depend on heavily, and I'm wondering what will happen going forward. Thanks, -- Chad _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
|||||||||||
|
|
Re: Rails upgrade
by Jeremy Lightsmith
::
Rate this Message:
I would love to schedule a skype call to do the release planning for the next release...after we get this one out :) I also have been pretty impressed w/ integrity's simpleness. I think it might be time to think about some changes.
Jeremy On Fri, May 22, 2009 at 9:24 AM, Brian Guthrie <bguthrie@...> wrote:
-- Jeremy Lightsmith Coaching Teams & Creating Communities 312-953-1193 http://onemanswalk.com/ (blog) http://facilitationpatterns.org/ (book in progress) http://www.linkedin.com/in/jeremylightsmith _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
|||||||||||
|
|
Re: Rails upgrade
by Chad Woolley
::
Rate this Message:
On Fri, May 22, 2009 at 1:39 PM, Jeremy Lightsmith
<jeremy.lightsmith@...> wrote: > I also have been pretty > impressed w/ integrity's simpleness. I think it might be time to think > about some changes. It also is lacking many important features that CCRB has (svn support, polling support, svn external/git submodule support, etc). Yeah, there may be some of these spread across various forks, but that doesn't help me now. It also seems very easy to get into dependency hell when developing/using it. Makes me appreciate CCRB's no-dependencies approach. CCRB does get a lot of things right, I think it just needs some update love and new killer features. -- Chad _______________________________________________ Cruisecontrolrb-developers mailing list Cruisecontrolrb-developers@... http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers |
| Free embeddable forum powered by Nabble | Forum Help |
