> That's a really cute idea :-)))) I was referring to the hello, world application. Compiling as in having no syntax/parser errors in the files modified since last commit.
But I admit, I wasn't realizing there is no 'central' compile. Anyways trunk seems to work again. Only new issues i've had is that the generator stopped respecting my QOOXDOO-URL in config.json It now defaults to /qooxdoo-trunk rather than using QOOXDOO-URL.. But I assume this is also temporary.. > Sometimes, especially so close to the next release (RC1), commits are > being made that break the trunk (e.g. to pass a code change quickly to a > co-worker). But these are usually minor glitches that are fixed with the > next revision. I regularly try to fix those flaws, only to find out I'm > running into a commit conflict with someone who was faster than me :). It's funny because near release you would expect a dont-break-trunk policy ;-) 2008/8/19 thron7 <[EMAIL PROTECTED]>: > Ralf Nieuwenhuijsen wrote: >> Question: sometimes when something does not work I update to SVN TRUNK. >> >> However, now, the trunk doesn't even compile. >> I can imagine it being unstable, but it suprises me that it doesn't >> compile at all?! >> >> You would expect the devs to compile before submit? >> > > That's a really cute idea :-)))) > > No, seriously. For one thing there is not a single "compile trunk". What > you compile in qooxdoo are applications, the framework itself has no > compile result. So you would compile one of the applications?! All of > them?! They might be broken in their own code, the framework being > innocent. Compiling all applications will take up to an hour, and you > still cannot be sure to have covered all possible classes of the > framework. Then some bugs only show when you actually run (or at least > load) the application, so compiling alone wouldn't be enough... > > But, yes, of course it would be desirable that developers test before > they commit. Alas, they are developers... ;) > > Sometimes, especially so close to the next release (RC1), commits are > being made that break the trunk (e.g. to pass a code change quickly to a > co-worker). But these are usually minor glitches that are fixed with the > next revision. I regularly try to fix those flaws, only to find out I'm > running into a commit conflict with someone who was faster than me :). > > So, bear with us. > > Thomas > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
