Comments (8)
The following items are needed for a major release, but not a point release (not a complete list):
(1) Per @sptramer :
A review of any and all "in-progress" banners that appear in docs should be carried out during every release stabilization period, before docs are frozen in the released set.
This would begin at the same time as stabilization is cut, at the beginning of hardening
(2) VS Upgrade tasks
from sig-release.
per #101 (reply in thread)
sig-graphics-audio can and should manage ASV releases.
Make sure this is included in release documentation
from sig-release.
@amzn-changml Can you weigh in on the need for VS upgrade tasks in the release process? is this still needed?
from sig-release.
It won't be needed unless the release:
- Has a blocking issue with VS between releases (at which case a point release should be considered)
- Has a major feature on the roadmap that requires the latest version of VS to be available
We do maintain a build node update cadence (defined here), but any bugs that arise from this during a release window will be part of the stabilization process
from sig-release.
@forhalle looking for your input here.
Based on the above response, any VS upgrade required seems to take care of itself for both 1 and 2, and the RM doesn't really need to do anything special, just be aware of this aspect of O3DE.
We have 2 options for documenting this:
A) a note in the release process mentioning 1) and 2)
OR
B) a task on the release project board which would require the RM to stop and think about this for each release.
from sig-release.
@tonybalandiuk - I do not understand how the upgrade "takes care if itself" for 2. I'm leaning towards a task on the release project board, but would like to understand this before giving my final opinion.
from sig-release.
@forhalle here's how I think it takes care of itself: If a major roadmap item requires a VS upgrade, then it would be up to the sig that owns that roadmap item or the contributor working on it to work with SIG-Platform and SIG-Build to get any support for VS in the build nodes. That roadmap item can't be submitted to the project unless that VS upgrade happens. So if the feature is in the release, then the VS support has been added. If it's not in the release, then it has not been added.
I don't see how sig-release would need to monitor this in any way or be involved in the management of the build system. So actually I'm leaning towards (A) as an FYI to the RM, and (B) seems unnecessary.
from sig-release.
@tonybalandiuk - Got it. In this case, I'm sticking with (A).
from sig-release.
Related Issues (20)
- [Pre Release] Prepare Build - 2 Days Before Release [Insert Date] HOT 1
- [Post Release] O3DE 24.09.0 Release: Ensure LFS binary objects are added and tested
- Confirm with with the O3DF marketing-committee all NON launch blocking Marketing requirements, if any, are complete after the release. These will be reviewed in SIG-Release meetings. If they are not completed, ensure a proper handoff.
- Cleanup - Delete the 24.09.0 stabilization branch
- [Planning] Ensure Marketing requirements are identified HOT 1
- [Planning] Create all Release tasks in this project board
- [Pre Release] Decides which o3de-extras gems are going to be part of the 24.09.0 release HOT 1
- [Pre-Release] Release Manager - Review Release Notes
- [Pre Release] Ensure Release Feature List is drafted and distributed
- [Pre Release] Author 24.09.0 Release Notes
- [Pre Release] O3DE 24.09.0 Release: at least 2 business days before release, Ensure PRs are created for branch merge for 5 Repos and AR validated
- [Pre Release] O3DE 24.09.0 Release: Confirm release branch is stable
- [Pre Release] O3DE 24.09.0 Release: Ensure version number updates to docs.o3de.org are staged (Required for Major Releases Only) HOT 1
- [Pre Release] O3DE 24.09.0 Release: Confirm all launch blocking Docs-Community SIG requirements are complete
- [Pre Release] O3DE 24.09.0 Release: Confirm all launch blocking Marketing requirements are complete
- [Pre Release] O3DE 24.09.0 Release: Ensure final release notes are documented, and a PR is created
- [Pre Release] Ensure the release milestone does not have any open issues. All issues in milestone must be resolved. If it is determined that a bug in the milestone will not be fixed for the release, it should be removed from the milestone.
- [Pre Release] O3DE 24.09.0 Release: Ensure installers are uploaded to S3 and the engine is set to 2.1.0
- Ensure editor splash screen installers reflect the current versions.
- Create the reverse integration sign-up sheet
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sig-release.