greg - Your assumption is incorrect.  We work completely off of Gemini, with maybe a few IMs, emails or team chats  to clarify requirements on a specific feature.  So whem someone points you to Gemini, they are pointing you to the only consolidated documentation that exists.  We are working to make the Gemini comments more clear, but that is not a simple fix.  In the end, we have been asked for more release documentation than we have the resources to produce at the moment.  We focused our initial efforts on making sure that Gemini contains all the release notes and once that problem is fully resolved, then we can move onto creating summary release documents.

I agree Gemini has improved 1,000% but Alex cannot do what he does not have..

Example:

http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1637/Default.aspx

http://support.dotnetnuke.com/issue/ViewIssue.aspx?id=6637&PROJID=2

As you can see, there is no documentation, details, etc.     This is common for new features, functionality..     often not in Gemini, when it is, it lacks details.   This would be ok if it was documented.

How did this feature get implemented if Gemini is used mostly for specs?

That is a major flaw in DNN.  No reasonable consolidated documentatiuon actually exists anywhere.  By 4.7.0 the documentation, limited as it is, in the documentation package is woefully inadequate.  Sifting through project blogs and forums can get you some information, and for anyone digging into Gemini there's a slim chance you'll find what you're looking for eventually, but DNN needs a documentation project.

Case in point are the various DNN books out.  By the time each is released, the book is incorrect.  Walkthroughs have entirely different screens than existed for the screenshots in the book.  Many on the core team would argue that the coe has stayed similar, and it all builds on itself pretty well, but unless you dig through the source that's of no use.  Heck, there's not even a forum for basic help questions.

DNN has matured.  Project management and documentation skills of the developers appears not to have kept pace.  Create a documentation project for Cambrian.  Require new releases to be documented before release.  Maintain the documentation.  And maintain two sets, a users/administrator's guide and a programmer's guide.

Jeff