Good point about the branches. I didn't realize that was being contemplated as well.
sean On Apr 1, 2005 5:35 PM, James Mitchell <[EMAIL PROTECTED]> wrote: > For trunk, it can be as little as a day or two or as much as a week. For a > branch, I'm guessing it will pretty much remain untouched except for > back-ported stuff and prep for a new release. > > I've already built and uploaded a build (via Maven), but I'm going to add > the Ant build ($ant dist) to this as well.....just gotta re-setup my linux > box to deal with Ant's requ'd commons-*.jar (the very reason I love Maven ;) > > I'm about 1/2 way finished....as I get a minute or two throughout the day, > I've been doing it all over putty to my box at home. It's going well, and I > hope to have this job setup to kick off at about 5AM (EST). > > I'll post when it is complete. > > > -- > James Mitchell > Software Engineer / Open Source Evangelist > Consulting / Mentoring / Freelance > EdgeTech, Inc. > 678.910.8017 > AIM: jmitchtx > Yahoo: jmitchtx > MSN: [EMAIL PROTECTED] > > ----- Original Message ----- > From: "Sean Schofield" <[EMAIL PROTECTED]> > To: "Struts Developers List" <dev@struts.apache.org> > Sent: Friday, April 01, 2005 5:26 PM > Subject: Re: 1.2.x nightlies? > > >> Instead of nightly, a better solution might be to only push a 1.2.x > >> nightly > >> if something changes. > > > > Interesting approach. That is similar to what Anthill does (its an > > open source tool for doing automated builds.) We use it at work and > > it builds hourly unless nothing has changed. I wonder how many days > > go by without a single commit though? > > > >> James Mitchell > > > > sean > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
