[WIP] Major Release Workflow
Engine
Admin Tasks
- Update the Stride repository README.md
- In the "Building from Source - Prerequisites" section, update the .NET SDK version references
- If there is a .NET SDK version upgrade:
- Update the Discord #welcome channel with new SDK version references. If you're unable to edit the message directly, copy its content, delete the original message, and then create a new one with the updated information
- Follow the steps outlined in the Docs Major Release Workflow
- Proceed with the steps in the Website Major Release Workflow
Developer Tasks
- Bump engine version (example commit)
- If there is a .NET SDK version upgrade:
- Aside from usual changes (example PR), one important thing is to update the prerequisites installer (example commit) and
global.json(example commit) - Also, add the new .NET Framework in VSPackage StrideCommandsProxy.cs (example commit)
- Aside from usual changes (example PR), one important thing is to update the prerequisites installer (example commit) and
- If there is a new Visual Studio released:
- Assuming there is no major breaking changes, simply updating the vsixmanifest so that it can do VS2022, VS2026 and any new versions is enough.
- Optional: Update Stride development NuGet packages version in all samples in
https://github.com/stride3d/stride/tree/master/samples- This is especially useful if there are asset upgrader taking a lot of time; otherwise, the default project upgrader will still be run on sample creation
- Open
samples\Stride.Samples.slnwith GameStudio. Let upgrade run, and do a "save all" from GameStudio; if there is any error opening the project, fix them and reset files before reopening (do not save incompletecsprojchanges without asset upgrades) - Bump versions in
sources\editor\Stride.Samples.Templates\ThisPackageVersion.PackageBuild.csandsources\editor\Stride.Samples.Templates\ThisPackageVersion.DevBuild.cs