Hey, I just want to pipe in and let you all know that I've been thinking a bit about this email that Jeremy sent out over the past week. It is really a model of grace and, well, congruence. I'm reading QSM v3 right now and have been thinking a lot about such things. Sorry for the interuption. Keep up the good work.
Emails like this make me want to keep on lurking, even though my new team is using Hudson. Bret On Mon, Jul 20, 2009 at 1:33 AM, Jeremy Lightsmith < [email protected]> wrote: > Brian, > > We definitely appreciate all the hard work you've been doing. Thank you. > > I did want to clarify one point though. We have have set the expectation > with our users that HEAD is a good, fairly stable place to point at. We've > told people to go to it if they wanted git support, or mercurial, for > example. And, with the ccrb team being so long between releases, many if > not most people that use ccrb right now are using it from HEAD. We've kept > it pretty stable and tight for quite a while now, though granted we haven't > made any huge changes in a while either. > > It sound like from what you're saying, at this point it would be easier to > go forward than back. So, Chad, can we get those stack traces? And, Brian, > if you don't have time, as Chad gives us more info, or if it might be a few > days before you do, can you let the list know so maybe one of us could look > at it? > > Again, this project has been barely alive for quite a while, and it's > really great to see some new blood breathing life into it. The team, and > really, the whole community, appreciate it, > > Jeremy > > > > On Sun, Jul 19, 2009 at 9:43 PM, Brian Guthrie <[email protected]>wrote: > >> Chad, >> >> I've resolved the port 3333 issue and a separate issue related to some >> work I've been doing with the Projects class that may or may not be >> related to what you're encountering. As for reading your config file, >> I haven't seen a stack trace with that so I'd appreciate it if you'd >> send it along. I haven't seen the issue with ~/.cruise either. >> >> Frankly I hadn't expected that too many people would be trying to >> build against HEAD as it's not stable. TW doesn't give me any paid >> time to work on this thing either so I'm what I can in the spare hours >> I have. Keep bringing issues up and I'll do my best to resolve them in >> a timely manner. And to answer your question, not only do I not see >> any particular reason to roll back the merge, I've pushed enough >> additional work since then that it would seem at this point infeasible >> to do so. Let me know if you feel strongly about it. >> >> Brian >> >> On Fri, Jul 17, 2009 at 2:31 AM, Chad Woolley<[email protected]> >> wrote: >> > Many things broken: >> > >> > - does not create ~/.cruise >> > - Blew up reading my config file, so I couldn't even start a builder >> > - no longer runs on port 3333 >> > >> > Basically, master doesn't even work. >> > >> > Is this gonna get fixed, or should we rollback this merge? >> > >> > Thanks, >> > -- Chad >> > _______________________________________________ >> > 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 > > -- Bret Pettichord Lead Developer, Watir, www.watir.com Blog, www.io.com/~wazmo/blog Twitter, www.twitter.com/bpettichord
_______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
