@@ -18,7 +18,7 @@ style board to track and prioritize issues.
1818
1919## Merging a pull request
2020
21- Please, make sure:
21+ Please, make sure:
2222
2323- Travis build is green
2424- At least one collaborator (other than you) approves the PR
@@ -84,3 +84,38 @@ guidelines are followed. If it is discovered that we have pushed a release in
8484violation of semver, than a patch release reverting the offending change should
8585be pushed as soon as possible to correct the error. The offending change can
8686then be re-applied and released with the proper version bump.
87+
88+ ## Live releasing the documentation
89+
90+ The documentation release script does a similar job to the release script except
91+ that it doesn't publish to npm. It will auto tag the current branch with
92+ a pre "docs" tag, and will push to documentation repository.
93+
94+ For a given tag (lets say ` 0.22.1 ` ) the first docs tag would be ` 0.22.1-docs.0 ` .
95+ In order to tags to be incremental and in order to include all the previous docs
96+ changes, make sure that if a docs tags exists for the current release,
97+ that you start from that tag.
98+
99+ To live patch the documentation in between release follow these steps
100+
101+ 0 . Find the latest documentation release.
102+ - Check the latest release tag (lets say ` v0.22.1 ` ).
103+ - Look for a docs-release tag for that version ex: ` v0.22.1-docs.X `
104+ - If one exists, check-it-out. If not checkout the latest release tag.
105+ - * Note: Checkout the tag and not master directly because some live
106+ documentation changes on master that could related to new components
107+ or updates for the upcoming release*
108+ 0 . Create a new branch from there (for example ` git checkout -b docs/v0.22.1 ` )
109+ 0 . Cherry-pick the commits you want to include in the live update
110+ ` git cherry-pick <commit-ish>... `
111+ 0 . Use the release-docs script to push and tag to the documentation repository.
112+
113+ * Note: The branch name you checkout to cherry-picked the commit is not enforced.
114+ Though keeping similar names ex: ` docs/<version> ` helps finding the branch
115+ easily.*
116+
117+ Example usage of release-docs script:
118+
119+ ``` bash
120+ $ ./tools/release-docs
121+ ```
0 commit comments