THIS IS A DRAFT

Recently the decision was made to aim for a 1.0 release including:

• A move to the latest, stable Roslyn packages
• A re-architecture of scriptcs, with a focus on distinguishing between an official public API (e.g. command line and hosting API) and the internal assemblies
• (Possible) Running on .NET core

This has several implications:

• We will need to move the minimum desktop framework dependency up to .NET 4.6
• There will likely be breaking changes across the board for scripts, script packs, modules, script libraries, hosts and any extensions

Work on 1.0 is taking place on the dev branch, which already has a large number of breaking changes since the merge of #1064.

Any patches applied to dev to fix bugs which are also present in the current 0.x release will be back ported to the current 0.x version on the support-0 branch. For new features added to the dev branch, we will selectively backport these to the current 0.x version on the support-0 branch. All 0.x releases will be made from the support-0 branch.

As 1.0 work on the dev branch progresses, we will periodically release pre-release 1.0 versions, starting with alpha, progressing through beta to RC, and eventually to a stable 1.0 release from master.

At the time of writing, there is one bug fix on dev that needs to be back ported into 0.x, #1114. There is also one feature on dev which is a candidate for a 0.x backport, #1086.

There are several other pull requests open which may also be considered for a back port if/when they are merged, e.g. #1109 and #1119.

Note that the upgrade to Roslyn packages 1.0.0 RC2 (currently merged to dev via #1064) is currently not scheduled for a back port to 0.x, although we may consider this. If this is done, it will be performed in a non-invasive manner with minimal breaking changes.