[UPDATE 2012-04-23 from the Drupal.org D7 Upgrade sprint: This list is rather old, outdated, and needs to be triaged by a maintainer before any further work is performed.]
Here's a list of all the issue's I've already submitted for future work -- things about the current system I'd like to improve, and issues other people have suggested. None of these were critical enough to delay the initial deployment of the system, but they should all be fixed eventually. I'm keeping this list updated (and roughly in priority order, as i see it) so there's a central place to keep track of future work.
- #107813: Ditch version selector box in favour of subtabs
- #89699: make release node form smarter when editing HEAD releases
- #90531: give non-admins a way to unpublish their own releases
- #112304: add setting to hide a given release series without unpublishing release nodes
- #97569: allow filtering issue queue by "series"
- #97145: always allow users to leave the version alone when replying to issues
- #93118: Print better error messages on faulty tag or branch name
- #90968: enforce sequential release tags in xcvs-taginfo
- #93055: add project type-specific settings
- #97568: allow maintainers to restrict choices for "Version" in new issues/replies
- #94137: email subscriptions for release nodes
- #94138: RSS feeds for release nodes
- #63491: Drupal Version-Module Support Matrix
- #96971: make better use of tabs and subtabs on project nodes
- #89535: add version filter to each project's "view all releases" page
- #89537: project-specific releases page needs sorting options
- #89673: add input filter to convert #12345 into a link to an issue
- #101905: add a way to stop automated packaging on a release node
Issues that will hopefully be addressed by Google Summer of Code proposal on translation tools:
- #105986: split contrib translations into their own directories and projects
- #92915: make translation status work in the new release system
Resolved/fixed items:
#105223: need to optimize packaging script to reduce load on DB server- #97173 (bug): Download link targets other project's tarball Fixed on 2006-11-12
- #87298: Add version info to modules page (5.x modules only) Fixed on 2006-11-21
- #100256 (bug): xcvs-taginfo doesn't properly associate core tags with project 3060 Fixed on 2006-11-29
- #98277: add project identification to .info files in packaging script Fixed on 2006-12-01
- #89538: need branch-aware notion of "default" or "latest" releases Fixed on 2006-12-06
- #89539: table of downloads on the project node, not just a "default release" link Fixed on 2006-12-06
- #97780 (bug): "Last updated:" does not get updated Fixed on 2006-12-07
- #101887: add setting to hide dev snapshot table on project nodes Fixed on 2006-12-09
- #101601: table of downloads when filtering by [all] versions in project browsing pages Fixed on 2006-12-17
- #97095 (bug): Issue tracker depends on project_release.module Fixed on 2006-12-25
- #108493 (bug): file_date updates from package-release-nodes.php not always saved to the DB correctly Fixed on 2007-01-19
- #97337 (bug): Module branch is not available as release target Fixed on 2007-01-21
- #111323: allow maintainers to see unpublished release nodes Fixed on 2007-01-29
- #94154: module page could say if new releases are available Fixed on 2007-07-11
- #105224: download table is broken if a release has no file attached Fixed on 2007-07-14
- #109181: provide feedback to owners when there are errors packaging releases Fixed on 2007-10-06