id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
9261	http://www.djangoproject.com/download/ needs updating	Karen Tracey	nobody	"This page lists 2 options (latest official or latest development -- trunk) for downloading.  I think the latest micro-release branch should be mentioned as an option -- it should provide bug fixes with less risk of instability due to new features coming in.  

Also under ""Which version is better?"" it still says backwards-incompatible changes may be made in latest development.  That should not be the case until 2.0 is on the horizon, right?  Currently as trunk is working on 1.1 there should be no backwards-incompatible changes made even on trunk.

Finally, only 0.96 is listed as a previous supported release, whereas I thought ""current and two previous"" mentioned in contributing doc would mean 0.95 would still be eligible for security fixes.  The last security fix, just prior to 1.0 going out, had fixes made to trunk, 0.96, 0.95, and 0.91.  Shouldn't only 0.91 have gotten bumped down to ""unsupported"" when 1.0 went out?"		closed	*.djangoproject.com	1.0		fixed			Unreviewed	0	0	0	0	0	0