This project is read-only.

vNext 1.8 or 2.0 ?

Topics: Core
Mar 25, 2014 at 2:45 PM
After upgrading to 1.x aka 1.8 I'm wondering if the next version shouldn't be called 2.0 ?

The main reasons for this Suggestion are:

1. the upgrade process is complex and requires planning

You might need to create an additional user before installing the new version as the default SuperUser can't access the Dashboard at all.

The upgrade itself consists of several steps and even drops existing tables in the database.

2. .Net Framework 4.5

The change of .Net Framework version means that all modules need to changed to 4.5 as well. We have a repo for each of our modules which are shared with the different solutions. So after updating a module for 1.8 the same module can't be used in 1.7.2 any longer. I won't expect such an incompatibility between minor Versions.

3. Marketing

Probably stupid - but I personally think that 2.x version gets more credability then 1.x versions.
Mar 25, 2014 at 10:24 PM
I just hit a breaking change in 1.8 :

"ContainerPart.ItemContentType" has been refactored to "ContainerPart.ItemContentTypes

I think a minor update (like 1.7.2 -> 1.8) should not include any changes breaking existing modules. So for me this is another indication that vNext should be called: 2.0