"I cannot tell a lie" - it was I who broke the build. In my confused mind when going home last night I had been imagining that the WAR build was not used except near release time and that it might not be too destructive to have it broken for a day... but that was clearly a silly idea! I guess this does point towards the merits of the "git-like" technologies where it would be possible to make a "going-home" commit without either branching 3 projects or breaking things for everyone :P

Thanks to Michelle for catching and fixing this problem, and apologies to all.

Antranig.


On 26/01/2010 10:01, Michelle D'Souza wrote:
Hi everyone,

It looks like a recent commit has broken the nightly build. This is a
particularly bad time as we have people who are trying to write test
plans and designers who are ensuring that as the developers furiously
churn out code we stay true to the designs. Developers, please test
before you commit - and don't forget to keep the stand alone config file
up to date. Just because something works for you when you run it from
Eclipse does not mean it will work on the nightly build. We are in the
unfortunate place where we don't have comprehensive unit tests to catch
regressions. That means that there is a greater responsibility on
committers.

This is meant to be a reminder to all of us. I haven't yet looked into
what is broken but will do so now. And if it's me who broke the build I
apologize in advance.
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to