It's confusing, but that's partly due to the history and capabilities of DNN at the time PE/EE were created.

If you look at other Opensource CMS's with a commercial end, you'll usually see it described as a "distribution" i.e. Drupal is the freeopen, and Acquia is their commercial distribution i.e. when making a new Acquia release they package up the latest drupal and add their pieces to it and that's the package.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Part of the reasoning was marketing I.e getting a boost from DNN's reputation, but also technical - DNN has rich extensibility support, so it's possible to upgrade virtually anything, meaning we could ship PE but later ship EE which PE users could choose to use i.e. upgrade their install but also add new capabilities.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US

Now we are using Evoq as the brand for the commercial products, there is no technical change, it's still the same as it was. From a management change, the platform team and evoq teams are completely separate, so can choose different release dates/frequencies/sizes as suits those teams. When packaging up Evoq, the evoq team select an appropriate platform build (to date always the most recent) and package that. I don't know the Evoq teams plans for matching platform releases, but at present I believe they've skipped one or two.

By doing this it means if platform works on a longer running project (e.g. dnn neXt) that might be six months or even longer for a release, Evoq can still provide regular updates for their customers.

 

***Apologies for the many posts, I am trying to debug a forums issue ***

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US