[Lazarus] Release schedule and policy

[Justin Smyth]

sent from my Telstra NEXTG™ handset

-----Original Message-----
From: Graeme Geldenhuys <graemeg.lists at gmail.com>
Sent: Monday, 25 October 2010 9:08 PM
To: Lazarus mailing list <lazarus at lists.lazarus.freepascal.org>
Subject: Re: [Lazarus] Release schedule and policy

Op 2010-10-25 11:37, Michael Van Canneyt het geskryf:
> 
> I just said 'it takes a lot of work', and you respond by making it 
> even more work ? :-)

Again, the person applying the patch simply need to do just that. Glance
over the patch to spot if the author of the patch was relatively sane,
apply the patch, run the test suite. If fine, commit.

The 'commiter' doesn't write the test cases, that's the job of the 'patch
author'. The patch author is the one doing most of the leg work: making
sure he/she has a test case to prove the patch, make sure it can be applied
without conflicts etc.


> To me, these statements sound contradictory, since LCL is a GUI framework ?

Not at all. Many of the LCL behaviour can indeed be tested for. Order of
firing events, making sure events actual do fire, the various UTF8 and file
wrapper functions etc, etc. There is even a Delphi + DUnit project on
SourceForge which is dedicated to testing of GUI applications (events
firing, tab order, button order etc.)



Regards,


[The entire original message is not included]