With the Drupal 7 code freeze upon us, it is high time for Ubercart to have a major version release on Drupal 6. That said, it's worth noting that Ubercart has been functional for some time, with over 9,300 installations reported to drupal.org in the module's usage statistics. Therefore, the lack of an official 2.0 release is arguably due to conservative release naming just as much as it is due to feature creep. The creep was mainly predicated by our desire to accommodate more users and contributed modules requiring a flexible pricing system. The final issues related to this price system's compatibility with VAT were hashed out in Paris, and by all appearances Ubercart will have a fully compatible VAT contributed module for the 2.0 release on Drupal 6.
Lyle and I met over lunch yesterday to develop a simple strategy for getting the 2.0 release out the door. I'll describe briefly what it will look like and then request your assistance.
Basically, we've gone through and tagged issues in the Ubercart issue tracker on drupal.org with "Release blocker." You can view all the release blocking issues and additionally filter that by their status. We've only marked critical issues, essential documentation issues, and low hanging minor / normal issues as blockers. Most feature requests, whether they have existing patches needing review or not, were bypassed intentionally. The obvious goal is to have a 2.0 as soon as possible, and that will certainly not rule out additional point releases to address the minor bugs and scalability issues that remain. If an issue was not marked as a release blocker, it doesn't mean we find that issue unimportant. We just have to prioritize or we'll never end up with a satisfactory release.
The list of blocking issues isn't that large - only 23 active issues by my last count. Even better, over half of those issues have patches ready for review. This means you can help quickly and easily! Information on applying patches for testing can be found at http://drupal.org/patch/apply.
Our plans at the moment involve a final release candidate by next Friday upon completion of these release blocking issues. These are the issues we are prioritizing. When they are closed, the release candidate will be rolled out and we'll do some final installation and update testing. We'll need more people to do update testing as well to make sure the various core modules are covered. After two weeks to let the dust settle and ensure no further critical issues come up, we'll call it a 2.0 and celebrate with a big fat pizza. Hooray!