[reportlab-users] Auto-testing and version numbers

Chris Withers reportlab-users@reportlab.com
Mon, 03 May 2004 08:18:22 +0100

Andy Robinson wrote:
> 5. Show the test suite output on www.reportlab.org (run with
> Python 2.3.3 initially) so the resulting PDFs are visible.

You could follow the Zope model here. They have a zope-tests mailing list which 
results are sent to, and there are a couple of frameworks for automatically 
running tests from CVS (easily adapted to subversion) using various python 
versions and various operating systems and emailing the results to a list... If 
you're interested, I could see about getting one of those scripts up and running 
for reportlab once you have your source control stuff how you want it.

Personally, one thing that would really help would be "official" releases of 
reportlab along the normal version number model:



x only changes on a framework rewrite.
y changes when new functionality is added
z changes when a bugfix release is done.

The most important thing is that .z releases ONLY fix bugs. So, you end up with 
multipel release branches, but you should end up with more stable software with 
less unexepcted breakage. The Linux model of a stable and unstable branch could 
also work ;-)



Simplistix - Content Management, Zope & Python Consulting
            - http://www.simplistix.co.uk