ashatora/openlayers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Replace ol3 with openlayers

Tim Schaub
2017-02-13 10:55:05 -07:00
parent 57bf00487d
commit 0db5715135
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Release-Procedure.md
+6 -6
@@ -9,7 +9,7 @@ Remember to open the developer console (hit `F12`) when running tests in IE9 oth
### Create a release branch
The release process involves a couple changes to the repository: updating the version number in package.json and adding a changelog. In order to make these release-related changes, create a branch in your ol3 clone. Note that all the examples below use 3.1.0 as the release version (and 3.0.0 as the previous release). You'll want to use the appropriate version numbers for the release you're working toward.
The release process involves a couple changes to the repository: updating the version number in package.json and adding a changelog. In order to make these release-related changes, create a branch in your repository clone. Note that all the examples below use 3.1.0 as the release version (and 3.0.0 as the previous release). You'll want to use the appropriate version numbers for the release you're working toward.
git checkout -b release-v3.1.0 master
@@ -21,9 +21,9 @@ Create a changelog for all merges to master since the previous release (see the
Edit the resulting changelog file with any summary notes or special upgrade considerations.
You can extract the upgrade considerations from the [`changelog/upgrade-notes.md`](https://github.com/openlayers/ol3/blob/master/changelog/upgrade-notes.md) file, by looking at any upgrade notes since the previous release.
You can extract the upgrade considerations from the [`changelog/upgrade-notes.md`](https://github.com/openlayers/openlayers/blob/master/changelog/upgrade-notes.md) file, by looking at any upgrade notes since the previous release.
If the [`changelog/upgrade-notes.md`](https://github.com/openlayers/ol3/blob/master/changelog/upgrade-notes.md)
If the [`changelog/upgrade-notes.md`](https://github.com/openlayers/openlayers/blob/master/changelog/upgrade-notes.md)
file does not already have a header for the current release, create a header with the version number (e.g. `### v3.1.0`).
Commit your changes:
@@ -68,7 +68,7 @@ Create a pull request and merge the release branch. This allows for any final r
### Tag
Tag the release. In a working copy of the openlayers/ol3 repo:
Tag the release. In a working copy of the openlayers/openlayers repo:
# tag the latest from openlayers/master
git tag -a v3.1.0 -m '3.1.0'
@@ -138,7 +138,7 @@ Move all open issues that are in the current milestone to the next one if needed
### Twitter
Tweet with the openlayers account, something like: "OpenLayers v3.12.0 is out! Thanks to everyone who contributed. https://github.com/openlayers/ol3/releases/tag/v3.1.0"
Tweet with the openlayers account, something like: "OpenLayers v3.12.0 is out! Thanks to everyone who contributed. https://github.com/openlayers/openlayers/releases/tag/v3.1.0"
### Notes
@@ -163,4 +163,4 @@ git cherry-pick <SHA_OF_BUG_FIX_COMMIT>
Since the `changelog.sh` relies on merge commits, and there won't be any merge commits between the previous release tag and your patch release branch, you'll need to manually create the changelog. Copy one of the existing changelogs for a patch release as a starting point. Link to the pull requests that included the original commits that you cherry picked above.
From this point, you can follow the normal release process ([after the changelog step](https://github.com/openlayers/ol3/wiki/Release-Procedure#update-packagejson)).
From this point, you can follow the normal release process ([after the changelog step](#update-packagejson)).