tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-06-28 15:39:40 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #6525 from open-sausages/pulls/4.0/improve-release-docs-v2

Browse Source 
More release docs improvements
This commit is contained in:
Damian Mooyman 2017-01-18 12:33:16 +13:00 committed by GitHub
commit f15f87b851
1 changed files with 3 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -260,6 +260,7 @@ subtasks which are invoked in sequence:
s3 bucket `silverstripe-ssorg-releases`. If you have setup your AWS profile
for silverstripe releases under a non-default name, you can specify this profile
on the command line with the `--aws-profile=<profile>` command.
See "Stage 3: Let the world know" to check if this worked correctly.
Once all of these commands have completed there are a couple of final tasks left that
aren't strictly able to be automated:
@ -278,12 +279,9 @@ aren't strictly able to be automated:
3.0 or 3.1) should usually be omitted.
* Set the github milestones to completed, and create placeholders for the next
minor versions. It may be necessary to re-assign any issues assigned to the prior
milestones to these new ones. See the below links for each module milestone list:
* [installer](https://github.com/silverstripe/silverstripe-installer/milestones)
* [framework](https://github.com/silverstripe/silverstripe-framework/milestones)
* [cms](https://github.com/silverstripe/silverstripe-cms/milestones)
milestones to these new ones.
* Make sure that the [releases page](https://github.com/silverstripe/silverstripe-installer/releases)
on github shows the new tag.
on github shows the new tag.
*Updating non-patch versions*