Release Testing

In order to ensure that our releases are well tested and as bug free as possible we need your help.

If you have a Trac installation with a combination of OS, database or frontend not represented in the list below, please consider adding yourself to the list.

What's expected of me?

Not much :) At the beginning of the release testing period you will receive an email from the release manager with details on where to download the release candidate. The email might also contain additional information on specific areas/features to test. But in most cases it's enough to verify that the release works as expected on your system.

Running the unit tests and functional tests and getting a green light would be a plus.

Once you have upgraded your server to the release candidate, please let us know by updating the corresponding release ticket (#8412 for 0.11.5). If you detect an issue, report it on that ticket as well.

Systems

Contact	Python	Database	Genshi	Frontend	OS
JonasBorgstrom trac.edgewall.org	2.5	PostgreSQL 8.3	0.6dev-r999	lighttpd + fastcgi	Ubuntu 8.10 X86_64
RemyBlank	2.3	SQLite 3.6.11	0.5-r1051	tracd	OS X 10.5
	2.5	SQLite 3.6.10	0.5-r998	apache + mod_python	Gentoo x86
Shane Caraveo	2.5	PostgreSQL 8.3		apache, mod_python, virtualenv	OSX 10.5
techtonik ​farmanager.rainforce.org	2.4	MySQL 5.0.67		apache, fastcgi, DreamHost	Debian 3.1
mathieu.ravaux@…	2.5	SQLite 3.5.9		apache + mod_wsgi	Ubuntu 8.10
saimen54@…	2.5	SQLite 3.3.4	0.5	tracd	WinXP x86
ChristianBoos	2.4.4	SQLite 3.3.8	0.6dev-r1052	apache + mod_python	SLES9 x86_64

Please indicate your e-mail address under "Contact".

rblank: How about keeping a single table with only contact info and configurations here, and using a "Release 0.11.4" ticket for testing coordination? People in the table above would be added to the CC: field when the ticket is created, and would report their findings as comments. Maybe for the next release?

cboos: yep, done so for 0.11.5, see #8412.