vNEXT Task: Beta Checklist

[StephenHodgson]

Overview

Beta release checklist

Requirements

• Project Builds and Runs for all supported platforms and configuration types
  • No Build warnings
• All Project Unity Tests pass
• Release asset packages should import and install without errors/warnings

Acceptance Criteria

A list of the specific things that must be done for approval / acceptance of the task in checklist form.
This may correspond with the above requirements.

• Fix Mrtk development serialization fix #2981 Fix service registration failures.
• Merge Updated MixedRealityToolkit Unit Tests #2984 All Unit Tests pass
  • Fix vNEXT: Unit Tests don't pass #2972 Fix unit tests
• Fix vNext: Incorrect type returned for the floor scale in the boundary visualization profile #2706 Boundary return type invalid
• Merge fixed Build Window layout in 2018.2+ #2948 Build Window Layout Fixes
• Merge Fixed editor texture asset loading #2988 fix for texture asset loading
  • Fix Inspector image assets don't load from relative path. #2987 Update asset references to not target the Asset folder in the root folder (e.g. Inspectors)
• Merge Added Copy/Paste functionality to configuration profiles. #2951 Copy/Paste/Clone Profiles
• Merge Consolidated setup prompts into one, and added VR setup #2983 Enable XR Settings on import.
  • Do vNEXT Task: Setup VR SDKs when configuring #2975 Setup XR SDKs if allowed.
• Merge Mixed Reality Editor Settings binary drop #2993 Mixed Reality Editor Setting binary drop
  • Fix Cannot import the MRTK in to a brand new Unity project using the Unity defaults. #2956 by creating MixedRealityEditorSettings.dll
• Merge initial pass at project clean-up and missing documentation. #2992 doc cleanup
  • Do Remove unused / unimplemented feature folders from the MRTK solution #2991 Update docs and clean up empty folders
• Merge Tidying up the Input System profile  #3001 Input System Profile tidy up
• Merge Spatial Awareness System "SpatialAwarenessParent" bypasses GameObject life-cycle check #2999 Spatial Awareness fixes
• Merge added null checks for controllers in input source events #3008 Fix null ref in controller finder
  • Fix Controller Finder sometimes gets null exceptions on source detected/lost #3007 Null ref in controller finder
• Fix Solver Demo Scene
  • In-Between solver demo does not work as expected #2996 In-Between Solver
  • Solver Demo Chase Source, Fixed Offset, and Face Headset not working properly #2997 Face Headset Solver
• Merge Fixed CameraCache fail if no camera tagged as main camera. #3024 CameraCache update
  • Fix If no tagged "Main Camera", the MRTK -> Configure fails badly #3021 Configuration fails if no main camera tagged in scene.
• Merge Mouse Input Fixes #3003 Mouse Input Fixes
  • Fix vNext: four copies of the mouse pointer are visible in OpenVR if the mouse has not been moved #2754 Fix OpenVR Mouse Input
• Do vNEXT Task: Create Getting Started Guide.md #2974 Create Getting Started Guide
• Fix [vNext] DragAndDropHandler moves with head #2960 Drag and Drop Handler
• Create Staging branches
• Update all feature branches with latest changes from mrtk_development
• Test & fix any discovered bugs
• Do vNext task: update version number for beta #2941 Update version number
• Create unity packages for mrtk_development and each feature branch

[david-c-kline]

We should get a conference call / chat session to discuss the above list. There are some things that can likely wait until after the first beta release (we plan on updating the beta every 1 - 2 weeks as we make changes).

[StephenHodgson]

These are the items are needed if we want a successful beta release. We also agreed to most/all of these items in the last shiproom meeting.

Please discuss concerns here.

[david-c-kline]

The last shiproom meeting discussed Spatial Awareness and bug fixes as being critical for beta. 2757 and Spatial Mouse were not discussed at all.

[david-c-kline]

[StephenHodgson]

Not having mouse support by default in our apps is like shipping a computer without a keyboard.

[david-c-kline]

Not having mouse support by default in our apps is like shipping a computer without a keyboard.

I don't see that. I have been developing mr/vr apps w/o mouse support for years.

What I was pointing out is that these changes were not brought up in shiproom when we agreed to take the spatial awareness merge and bug fixes for beta. Also, 2757 feels like a rather large item and i do not recall having discussions on the correct intelligence for it.

There will be more beta releases before rtw. We can address these as we go.

[StephenHodgson]

I'm not so sure spatial awareness should be merged in as it is largely untested.

[StephenHodgson]

I don't see that. I have been developing mr/vr apps w/o mouse support for years.

As your customer I am telling you have I have a legitimate business need to have this in beta.
If I fix it before then, I fully expect you to review, test, and merge it in before we release.

[david-c-kline]

I'm not so sure spatial awareness should be merged in as it is largely untested.

Kurtis and I have been testing this feature branch for as long as it has existed.

[StephenHodgson]

Awesome, now let's get the rest of the community to test it before it makes it into development :)

But I think the priorities are getting bug fixes in first before we add new features that may (or may not) contain bugs.

[david-c-kline]

Spatial has been on the radar and being actively communicated, developed and reviewed for weeks. I completely disagree that it is not a priority, especially when talking with customers.