Re: Kudos - keep up the hard work!

[Jan Ischebeck]

On 17 Oct 2002 08:22:48 Derek Neighbors <address@hidden> wrote:
> This and some other release type issues makes me wonder about road
> maps.  Should we fix a few things and do a 0.4.1 release of things or a
> 0.5.0 and then begin roadmapping for the future? =20
> 
> Jason/Jan???

IMO the main problem with this release seems to be that there were many 
changes and too little testing of the prereleases. 

Although roadmapping could solve some release type issues, because you
can plan things more concrete, it is not the most important part needed to get
a release, which is working in 90% percent of all cases.

More important is to document which parts of the gnue prereleases are
tested on which platforms. (f.e. appserver was not tested in combination with 
python2.2, etc.)

To reach this goal,  we need to define

1. a list of platforms/configurations to test:
"Debian Woody (deb install,python2.1),Debian Sid (setup-cvs.py,python2.2), 
Windows (setup.exe,python2.2)" should be the minimum

2. a list of tests to run: 
I thought of something like http://www.mozilla.org/quality/smoketests/.
there are already some test cases in the samples/testcases directory.
testing should be made as easy as possible, f.e. file
samples/testcases/testrun.gpd can be used to start all forms in the
subdirectories of samples/testcases.


3. a way to document which testcases were tested on which configurations
   and if they worked or not.

The status of testing efforts could be shown on a web page. like:
http://www.openoffice.org/dev_docs/source/643/release_notes.html#qa 

for now a simple php script which creates a web page out of database
records and a gfd file to populate the database would be sufficient.

A web form to add/change entries would be the next step. Later this
functionality could be implemented in DCL.



Although having a fixed testing environment will be another thing to be
maintained (and to be created), but it will help to increase the QA of
gnue, and there will be one point in the nearer future, when it will
become mandatory.


Jan


---------------------
Jan Ischebeck e-Services
address@hidden