On Thu, 2013-10-24 at 15:22 +0100, Alex Valavanis wrote:
@Josh - Yes, it would be great to hook up the Google test stuff eventually, but I'd be happy with just fixing the last couple of issues with the cxxtest suite for the time being. Maybe "robust" was the wrong word! Similarly, I think it should be fairly straightforward to add the rendering tests into "make check". As such, this would make v1.0 a usable benchmark release for limited automated regression testing of some aspects of the code.
As for the GTK+ 3 stuff, yeah, I agree that it'll take a lot of testing before we endorse user-builds so we can put it on hold. However, we should probably aim to fix up the known bugs http://goo.gl/06WnfD. I just don't feel very confident about stamping "This is a stable release" on something that has such a crappy build option available, even if it is marked as an experimental feature.
Sounds like you have two more reasonable bug or blueprint proposals to attach to the 1.0 milestone.
Please keep the 1.0 release process tidy by including these in the project system.
Best Regards, Martin Owens