tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 12:05:37 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #9055 from open-sausages/pulls/4/release-docs-update

Browse Source 
DOCS: Ensure minor releases follow security release steps
This commit is contained in:
Robbie Averill 2019-06-12 11:02:15 +12:00 committed by Aaron Carlino
commit 4eb5800532
2 changed files with 1 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/en/04_Changelogs/4.4.0.md
View File

@ -240,8 +240,6 @@ conditions.
Yes, it will attempt to find the most recent public "hash-less" URL
for this file and redirect to it.
<<<<<<< HEAD
<<<<<<< HEAD
### Changing the file resolver
The file resolution strategy describes how files are resolved. It relies on a list of file helpers and will iterate through them when looking up files.

2
docs/en/05_Contributing/05_Making_A_SilverStripe_Core_Release.md
View File

@ -479,7 +479,7 @@ will need to be regularly updated.
* Update the [Slack](https://www.silverstripe.org/community/slack-signup/) topic to include the new release version.
* For major or minor releases: Work with SilverStripe marketing to get a blog post out.
They might choose to announce the release on social media as well.
* If the minor or major release includes security fixes, follow the publication instructions in the [Security Release Process](#security-release-process) section.
## See also