Hello all,
Here's a status on the new Repository release.

The original target date was the end of February 2007, and obviously that didn't happen as some personal issues prevented me from spending the amount of time necessary to close ALL open bugs in Gemini. But enough with the excuses. Here's where I am .. and here's the plan to get the next release out.

Road Map :: http://support.dotnetnuke.com/project/RoadMap.aspx?PROJID=22
The Road Map shows the issues from Gemini that will be fixed/implemented. I built the road map from ALL the open bugs that were listed at the beginning of February, plus some of the more requested enhancements.

In case you're not familiar with Gemini/the Road Map, the Status column will be one of 4 different values, Assigned, Checked-In, Reopened or Closed. Assigned means that I have not fixed the issue yet. Checked-In means that I fixed the issue and have checked the fix into our source control server. Reopened means I thought I fixed it, checked the fix in but Mike and/or Barton tested it and have decided that I did not sufficiently fix the issue, so I need to go back and try again. Finally Closed means that Mike and/or Barton have tested the fix and agree that the issue is fixed.

Knowing that, you can review the Road Map at any given time to see where we are in the process. Currently, as I write this, the Road Map looks like this...

25 Total issues/enhancements to be implemented
10 issues are Closed
05 issues are Checked In, waiting to be tested
09 issues are Assigned, waiting to be fixed
01 issue is reopened and needs to be re-fixed

In terms of timeframe, and to help you gauge the effort remaining, I need about 2 days to fix the remaining 10 remaining issues. Then there will be the testing time for Mike and Barton to test and mark the issues as closed or to reopen any issues that I didn't fix properly.

The milestone we're all looking forward to is for all 25 items to have a status of Closed. Once that happens, then the module enters the DotNetNuke Release Process. 

If you are not aware, a few months ago the core team implemented a formal release process for all core modules. It manages and tracks all the things that have to happen before a new public release of a core module is published ( there's a lot, believe me ) . I was heavily involved in the definition of the process, and in fact, wrote a DNN module to track module submissions all the way through the process. I will begin blogging on the process in detail shortly as this module will soon be made public. Anyway, what we are seeing is that it takes on average 10 days for a release to get all the way through the process .. some quicker, some longer, but on average 10 days or so.

I appreciate all your patience, I know it's been a long time since the last Repository update and no one wants this next release out as much as I do. Personal issues have subsided and my #1 priority now is to get the remaining Road Map items closed, release the update, then begin working on version 4.0 :)