There's plenty of hardware for things like this. It's just a matter of spending some quality time with infrastructure, preferably by IRC [and I think everyone knows how much I adore IRC :)].
* http://apache.org/dev/infra-volunteer.html Several projects have their own zone on helios now: * http://apache.org/dev/machines.html -T. On 7/6/05, Larry Meadors <[EMAIL PROTECTED]> wrote: > That sounds reasonable to me. I would be more than willing to set up a > box to do the builds here if there is not one at apache to use. > > Does anyone know if there is one already? > > Larry > > On 7/6/05, Ted Husted <[EMAIL PROTECTED]> wrote: > > All ASF projects are expected to provide automatic nightly builds. We > > just haven't gotten to around to that yet. The nightly builds live for > > seven days each, and then get recycled, so as to not eat up too much > > disk space. > > > > Any non-automatic release is generally tagged with a sequential > > version number. After someone rolls it, we vote on it's quality: > > Alpha, Beta, General Release. A release can start out as Alpha and > > work its way up to General Release as more people try it. A release > > can also be downgraded if a problem is found later. > > > > Of course, since the Subversion revision numbers are essentially tags, > > we could also snag any given nightly build (once we have them) and > > designate it "version #.#.#", making a note in our status file that > > version #.#.# corresponds to SVN revision ####. > > > > Later, if we ever need to branch, we can branch on a revision number > > as easily as a tag. > > > > -Ted. > > > > On 7/5/05, Sven Boden <[EMAIL PROTECTED]> wrote: > > > > > > Not specific to the problem below. But what about providing iBATIS > > > development releases, e.g. after every big round of SVN changes. Most > > > other projects seem to do it. > > > > > > A few advantages I see: > > > - It's easier to tell people: "test with the development jar files" > > > than "extract the sources from SVN, compile and test" > > > - Better quality of releases as more people would already test/use the > > > development releases. > > > - Less "pressure" to release new versions. > > > > > > Regards, > > > Sven Boden > > > > > > > > > On Tue, 5 Jul 2005 07:29:03 -0600, you wrote: > > > > > > >As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good > > > >to > > > >go! > > > > > > > >Cheers, > > > >clinton > > > > > > > >On 7/5/05, Guido García Bernardo <[EMAIL PROTECTED]> wrote: > > > >> > > > >> Hi, > > > >> > > > >> I am facing with this bug: > > > >> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5 > > > >> > > > >> Is there any release plan for 2.1.5 so that I can decide whether or not > > > >> I'll need to use 2.0.9b or compile the source? > > > >> > > > >> Thank you very much. > > > >> > > > >> -- > > > >> Guido García Bernardo - [EMAIL PROTECTED] > > > >> Tfn. +34 983 54 89 08 > > > >> ITDEUSTO - Valladolid
