...
Explain that a release has 3 states - Initialized, Release Draft, and Published.
Log in as a developer user - sermdev.
Create a new release.
Point out that it is in the Initialized state.
Create another release. Point out that there can be multiple releases in the initialized state. But there can be only one release in Release Draft or Published state. Multiple initialized releases are allowed for planning purpose.
Release in the Initialized state has no content yet, so it won’t appear on the list of branches of the CC. Go to CC View/Edit page and show that no branches for the releases in the Initialized state.
Go back to release page and create a Draft.
Assign content to the release. You may choose not to assign some content to the release because it is for a future release or you simply don’t want it, e.g., in Deleted state.
Run validation. Show invalidity, like there is a necessary ASCCP in WIP state that is not included.
Fix the issue. Validate again.
Create the draft release.
Show that the draft release now appears on the CC View/Edit page for viewing and reviewing only.
At this point people can be invited to review the release and give comments.
Point out that more CCs can be added or changed in the Working branch.
If all reviews have been gathered and changes need be made to the release draft, the release needs to be taken back to Initialized. Revert to initialized.
Now you can go back and add a property to an ACC by taking it back to the WIP state.
Create the release draft again. This time published it.
Show that now there is the Published release branch on the CC View/Edit page.
The end.
Ep4. Managing a developer Code List
Ep5. Managing End User Core Component
Ep6. End User Core Component and BIE Extension
Ep7. Collaborative CC development
Show CC development. Emphasizing the Commenting feature. Transfer ownership. Talk more about states. Talk about Deleted CCs.
...