Project issue tracking 5.x-2.3 release roadmap

It's time to fix the last of the bugs before we create a new branch and start committing D6 porting patches for project*. That means we need a 5.x-2.3 release of Project issue tracking. Here's the working list of issues to resolve before we can tag/release the next version.

• http://drupal.org/node/98278 project* namespace bugs in $node
• http://drupal.org/node/324620 "Code style fixes on 5.x-2.x"
• http://drupal.org/node/326419 validating Version and Assigned against potentially the wrong project -- Fixed 2008-11-17
• http://drupal.org/node/283332 {project_issues} table not being created when module is enabled -- Fixed 2008-11-15
• http://drupal.org/node/311369 Project loading could use the static cache -- Postponed until 6.x
• http://drupal.org/node/254416 Change of project in comment does not update assigned options -- Fixed 2008-10-26
• http://drupal.org/node/275323 project_issue_generate_issue_comments() causes fatal errors in some cases -- Fixed 2008-10-23
• http://drupal.org/node/311539 "Malicious attempt to access unauthorized information detected" error

If someone wanted to really be cool, they'd work on this, too:

• http://drupal.org/node/201435 Huge list of projects hard to use, can hang browser

It'd be a really nice UX improvement, but it's not exactly a bug, so I don't want to hold up the release for this. But, if a good patch appeared, I'd be happy to try to get it in, too.