mirror of
https://github.com/silverstripe/silverstripe-framework
synced 2024-10-22 14:05:37 +02:00
DOCS Clarify sec release process
This commit is contained in:
parent
dd4bcac3a7
commit
1f881f5c3f
@ -182,6 +182,8 @@ Follow these instructions in sequence as much as possible:
|
|||||||
* Send out a note on the pre-announce list with a highlevel description of the issue and impact (usually a copy of the yet unpublished security release page on silverstripe.org)
|
* Send out a note on the pre-announce list with a highlevel description of the issue and impact (usually a copy of the yet unpublished security release page on silverstripe.org)
|
||||||
* Link to silverstripe.org security release page in the changelog.
|
* Link to silverstripe.org security release page in the changelog.
|
||||||
* Move the issue to "Awaiting Release" in the [project board](https://github.com/silverstripe-security/security-issues/projects/1)
|
* Move the issue to "Awaiting Release" in the [project board](https://github.com/silverstripe-security/security-issues/projects/1)
|
||||||
|
* Perform release
|
||||||
|
* Follow the steps for [making a core release](making-a-silverstripe-core-release)
|
||||||
* After release
|
* After release
|
||||||
* Publish silverstripe.org security release page
|
* Publish silverstripe.org security release page
|
||||||
* Respond to issue reporter with reference to the release on the same discussion thread (cc security@silverstripe.org)
|
* Respond to issue reporter with reference to the release on the same discussion thread (cc security@silverstripe.org)
|
||||||
|
@ -161,7 +161,7 @@ Check all tickets assigned to that milestone are either closed or reassigned to
|
|||||||
Use the [list of all issues across modules](https://www.silverstripe.org/community/contributing-to-silverstripe/github-all-core-issues)
|
Use the [list of all issues across modules](https://www.silverstripe.org/community/contributing-to-silverstripe/github-all-core-issues)
|
||||||
as a starting point, and add a `milestone:"your-milestone"` filter.
|
as a starting point, and add a `milestone:"your-milestone"` filter.
|
||||||
|
|
||||||
Merge up from other older supported release branches (e.g. merge `3.1`->`3.2`, `3.2`->`3.3`, `3.3`->`3`, `3`->`master`).
|
Merge up from other older [supported release branches](release-process#supported-versions) (e.g. merge `3.1`->`3.2`, `3.2`->`3.3`, `3.3`->`3`, `3`->`master`).
|
||||||
|
|
||||||
This is the part of the release that prepares and tests everything locally, but
|
This is the part of the release that prepares and tests everything locally, but
|
||||||
doe not make any upstream changes (so it's safe to run without worrying about
|
doe not make any upstream changes (so it's safe to run without worrying about
|
||||||
|
Loading…
Reference in New Issue
Block a user