Next release of the Engine

[sgold]

@sgold

Here’s a proposed action plan for the release:

1. Create a “v3.5.0” Engine milestone at GitHub, without a due date.
2. Target closed issues and PRs to the new milestone if they’ve been solved/integrated since v3.4.
3. Open issues as needed for ideas that emerge (or have emerged) from this discussion.
4. Target open issues and PRs to the new milestone if they seem like promising candidates.
5. Publish an alpha version for testing, with a list of changes since v3.4.0 .
6. Announce a feature-freeze date.
7. After feature freeze, create a “v3.5” branch at GitHub and publish a beta version for testing.
8. During beta test, integrate low-risk bug fixes from master into “v3.5”.
9. Announce a code-freeze date.
10. After code-freeze, publish the “v3.5.0” release.

currently on step 8

I could use more help with beta testing. See the thread V3.5.0 beta testing