Jonas Borgström wrote: > Most issues seems to have been fixed in 0.11-stable already but are > there any other bug fixes that need to go into 0.11.4 as well?
I'd like to fix the following ticket for 0.11.4: http://trac.edgewall.org/ticket/8059 > What is the best approach? Pre-release testing checklists, release > candidates or both? I would suggest at least one release candidate, and trying to enlist a few people with various architectures and configurations (OS, database, web server, front end) for testing. I'm sure we can find a few people on this list who would be willing to test release candidates on their setups. A standard testing procedure would be nice, but longer term we should try to automate the procedure completely. A script that installs Trac from a tarball or SVN tag, creates a new environment, and performs and checks various operations on it would be very useful. There is some overlap with functional tests, maybe they should just be extended to allow using e.g. other databases, and to operate on an environment created from scratch. Not related to 0.11.4, we should also diversify the configurations on which the automatic unit tests are run. I am in the process of setting up an OS X machine with Python 2.3 - 2.6, and a Windows VM. Could these be used as build bots for t.e.o? -- Remy
signature.asc
Description: OpenPGP digital signature
