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 be added to the CC list of the release ticket, where you will find details on where to download the release candidate. The ticket might also mention 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. See Testing Scenarios below for some suggestions.

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

Current release: 0.11.6, tracked in #8840.

Systems

Contact	Python	Database Backend + Bindings	Genshi	Web Frontend	OS	Subversion	Testing
JonasBorgstrom trac.edgewall.org	2.5	PostgreSQL 8.3 + psycopg2 2.0.8	0.6dev-r999	lighttpd + fastcgi	Ubuntu 8.10 X86_64	svn 1.5.1	prod

ChristianBoos

2.4.4

SQLite 3.3.8 + PySqlite 2.5.0

0.6dev-r1052

apache + mod_python

SLES9 x86_64

svn 1.6.3

prod

Note: no php	2.6.1 [MSC v.1500 32 bit (Intel)]	MySQL server: "5.0.67-community-nt", client: "5.1.33", thread-safe: 1 + MySQLdb 1.2.3c1	0.6dev-r1060	tracd	Windows Vista (x64) sp1	svn 1.6.2	dev
		SQLite 3.5.9 + PySqlite 2.4.1					dev
		PostgreSQL 8.3 + psycopg2 2.0.8					dev

Note: no (docutils, php, pygments, pytz)	ActivePython 2.5.4 [MSC v.1310 32 bit (Intel)]	MySQL server: "5.0.67-community-nt", client: "5.0.27", thread-safe: 1 + MySQLdb 1.2.2	0.6dev-r1028			svn 1.6.3	devlite
		SQLite 3.3.4 + PySqlite 2.3.2					devlite
		PostgreSQL 8.3 + psycopg2 2.0.10					devlite

Note: no (lxml, svn, docutils, php, pygments, pytz)	2.4.4 [MSC v.1310 32 bit (Intel)]	MySQL server: "5.0.67-community-nt", client: "5.0.27", thread-safe: 1 + MySQLdb 1.2.2	0.6dev-r1052			no svn	devlite
		SQLite 3.6.2 + PySqlite 2.5.1
		PostgreSQL 8.3 + psycopg2 2.0.10 (dt dec ext pq3)

Note: no (lxml, svn, docutils, php, pygments, pytz)	2.3.5 [MSC v.1200 32 bit (Intel)]	SQLite 3.6.2 + PySqlite 2.5.1	0.5.1			no svn	devlite
		PostgreSQL 8.3 + psycopg2 2.0.10					devlite

RemyBlank	2.3	SQLite 3.6.20	0.5-r1051	tracd	OS X 10.5	svn 1.6.5	dev
	2.6	SQLite 3.6.19	0.5-r1051	apache + mod_python	Gentoo x86	svn 1.6.5	dev

Shane Caraveo	2.5	PostgreSQL 8.3		apache, mod_python, virtualenv	OSX 10.5
Anatoly Techtonik	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.1	tracd	WinXP x86	1.5.6
lists@…	2.5.4	SQLite 3.6.13	0.6dev-r1052	mod_wsgi 2.4	Ubuntu 6.1	1.5.6	prod

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

Testing Scenarios

The above configurations are used in to the following test conditions, along with corresponding expectations.

prod

• version is used in "production", on a heavily used site (public or private)
• no regression or new defect should be reported by the users

dev

• full test suite pass (both unit tests and functional tests)
• testing creation of a new environment, using a Trac mirror for the repository
• interactive testing of that new environment
• memory usage should stay steady and performance should be adequate

devlite

• full test suite pass (both unit tests and functional tests)
• interactive testing of existing environment
• memory usage should stay steady and performance should be adequate

(expand as needed)