You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* add doc links
* update SBOM lite
* update augmented SBOM
* Prepare to generate r4.1.0 release documentation
* add CHANGELOG entry for next minor release
* remove step to update the SSDLC Report spreadsheet
** The spreadsheet was only used for internal tracking. Coverity tracks static analysis issues. And third party vulnerabilities are tracked in third_party_vulnerabilities.md.
* move `#` comment outside of `snyk_args` to avoid bash error
* update `etc/apidocmenu.md` before generating docs
** The `doxygen-latest` target builds from the tag. Update `apidocmenu.md` before tagging, to ensure the updates are present in the built docs.
* remove duplicate sentence
Copy file name to clipboardExpand all lines: etc/releasing.md
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -148,8 +148,6 @@ Ensure the `sbom` task is passing on Evergreen for the relevant release branch.
148
148
149
149
Review the contents of the new Augmented SBOM and ensure any new or known vulnerabilities with severity "Medium" or greater have a corresponding JIRA ticket (CXX or VULN) that is scheduled to be resolved within its remediation timeline.
150
150
151
-
Update the [SSDLC Report spreadsheet](https://docs.google.com/spreadsheets/d/1sp0bLjj29xO9T8BwDIxUk5IPJ493QkBVCJKIgptxEPc/edit?usp=sharing) with any updates to new or known vulnerabilities.
152
-
153
151
Update `etc/third_party_vulnerabilities.md` with any updates to new or known vulnerabilities for third party dependencies that have not yet been fixed by the upcoming release.
154
152
155
153
Download the "Augmented SBOM (Updated)" file from the latest EVG commit build in the `sbom` task and commit it into the repo as `etc/augmented.sbom.json` (even if the only notable change is the timestamp field).
@@ -207,6 +205,8 @@ git fetch upstream
207
205
git checkout releases/vX.Y
208
206
```
209
207
208
+
In `etc/apidocmenu.md`, update the list of versions under "Driver Documentation By Version" and the table under "Driver Development Status" with a new entry corresponding to this release.
209
+
210
210
Update `CHANGELOG.md` with a summary of important changes in this release. Consult the list of related Jira tickets (updated ealier) as well as the list of commits since the last release.
211
211
212
212
Remove the `[Unreleased]` tag from the relevant patch release section, e.g. for release `1.2.3`:
@@ -222,7 +222,7 @@ Remove the `[Unreleased]` tag from the relevant patch release section, e.g. for
222
222
223
223
```
224
224
225
-
Commit and push the updates to `CHANGELOG.md` to `releases/vX.Y` (a PR is not required):
225
+
Commit and push the updates to `etc/apidocmenu.md` and `CHANGELOG.md` to `releases/vX.Y` (a PR is not required):
In `etc/apidocmenu.md`, update the list of versions under "Driver Documentation By Version" and the table under "Driver Development Status" with a new entry corresponding to this release.
242
+
241
243
Update `CHANGELOG.md` with a summary of important changes in this release. Consult the list of related Jira tickets (updated earlier) as well as the list of commits since the last release.
242
244
243
245
Remove the `[Unreleased]` tag from the relevant non-patch release section, e.g. for release `1.3.0`:
@@ -256,7 +258,7 @@ Remove the `[Unreleased]` tag from the relevant non-patch release section, e.g.
256
258
> [!IMPORTANT]
257
259
> If there are entries under an unreleased patch release section with the old minor release number, move the entries into this release's section and remove the unreleased patch release section. For example, for a `1.3.0` minor release, move entries from `1.2.3 [Unreleased]` to `1.3.0` and remove `1.2.3 [Unreleased]`. Due to cherry-picking, a non-patch release should always (already) contain the changes targeting a patch release with a prior minor version number. (This is analogous to updating the fix version of Jira tickets, as done earlier.)
258
260
259
-
Commit the updates to `CHANGELOG.md`.
261
+
Commit the updates to `etc/apidocmenu.md` and `CHANGELOG.md`.
@@ -525,7 +528,7 @@ This branch will be used to create a PR later.
525
528
> [!IMPORTANT]
526
529
> Make sure the `post-release-changes` branch is created on `master`, not `rX.Y.Z` or `releases/vX.Y`!
527
530
528
-
In`etc/apidocmenu.md`, update the list of versions under "Driver Documentation By Version" and the table under "Driver Development Status" with a new entry corresponding to this release.
531
+
For a patch release, in`etc/apidocmenu.md`, update the list of versions under "Driver Documentation By Version" and the table under "Driver Development Status" with a new entry corresponding to this release.
529
532
530
533
In `README.md`, sync the "Driver Development Status" table with the updated table from `etc/apidocmenu.md`.
0 commit comments