Confusing Note About Script Assembly Definition Files in 2017.2 RC1 Release Notes

[SonicBloomEric]

I noticed the following bullet in the Release Notes for RC1:

Editor: Added assembly definition files feature for script compilation pipeline in the editor. Allows you to define your own managed assemblies based upon scripts inside a folder. By splitting your project’s scripts into multiple assemblies, script compilation times in the editor can be greatly reduced. Note that the latest version of Visual Studio Tools for Unity is required for this feature to work with solution and project generation for Visual Studio.
Feature was disabled in 2017.2.0b11 because development did not finish in time for release.

The bold emphasis is mine.

@lukaszunity mentioned in [another thread]( Example Project - Assembly Definition Files page-2#post-3211467) that the feature won’t appear in 2017.2, but is slated for 2017.3.

[mention|+Zx8XggHCmmryYQOXi4vxg==], any insight into this? (Asking you because you announced the RC ;D) If it truly is “delayed until 2017.3” then perhaps that “2017.2 feature” should either be:

• entirely scrubbed from the release notes, or
• amended to include a note saying “We expect this feature to appear in 2017.3.”

Thoughts?

[SonicBloomEric]

Slightly less confusing, but the Release Notes also contain the following:

Scripting: Editor: Load precompiled managed assemblies (.dlls) and assembly definition file assemblies on startup even if there are compile errors in other scripts.

Perhaps this should also be scrubbed from the release notes if assembly definition files support has been delayed until 2017.3…

[CarlosRincon]

Hi

Apologies for the confusing release notes, I meant to amend this before issuing the RC. The feature is indeed postponed until 2017.3. Will amend the notes for RC1, and ensure they are also clear for future RCs and the final release.

Thanks for the heads-up!