----- Original Message ----- From: "Jordi Salvat i Alabart" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "JMeter Developers List" <[EMAIL PROTECTED]> Sent: Friday, February 06, 2004 12:36 AM Subject: Nightly builds & releases [Was: Re: DO NOT REPLY [Bug 26612] - Listener: Mailer Visualizer does not start up]
> We maintain one single codebase at this moment -- no branches. Nightly > builds are a strange beast: they are compiled using whatever was in CVS > HEAD at that time, but against the latest CVS versions of all Jakarta > libraries (like ORO, Commons, Avalon, etc.), not the ones the developers > use or the ones the release will ship with. Actually, there are now *two* Gump builds - one against the latest of everything, and another uses the jars in CVS. The zipped jars are created from the CVS build, so correspond well with a release. > Which brings up a point (and this is the reason for CC this to > jmeter-dev): we should not rely on Gump nightlies as a replacement for > frequent releases, as we tend to do now. The intent of Gump nightlies is > to have future-proofing development: a way to reduce the chances that > future releases of libraries we depend on will break our stuff. They're > often not good as point releases for users to try out. Yes and no - the zips are created and saved even if the test fails miserably, and at present the test logs are not preserved from day to day. > > Remember ESR's moto in CATB? "Release Early, Release Often": > http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html > > We should make an effort in this sense and try to have at least monthly > point releases -- weekly even better. Call them beta if you wish... S. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
