Skip to content

Commit b454b02

Browse files
committed
docs: update release-docs in CONTRIBUTING.md
- remove ember testing - add docs for updating the website. - add list of required accesses to publish
1 parent 7adc19a commit b454b02

File tree

1 file changed

+14
-14
lines changed

1 file changed

+14
-14
lines changed

CONTRIBUTING.md

+14-14
Original file line numberDiff line numberDiff line change
@@ -89,21 +89,15 @@ You can use the following scripts to make sure that the travis-job does not fail
8989
- **npm run integration-test** will run integration tests (using old NodeJS versions and integrations with webpack, babel and so on)
9090
These tests only work on a Linux-machine with `nvm` installed (for running tests in multiple versions of NodeJS).
9191

92-
## Ember testing
93-
94-
The current ember distribution should be tested as part of the handlebars release process. This requires building the `handlebars-source` gem locally and then executing the ember test script.
95-
96-
```sh
97-
npm link
98-
grunt build release
99-
cp dist/*.js $emberRepoDir/bower_components/handlebars/
92+
## Releasing the latest version
10093

101-
cd $emberRepoDir
102-
npm link handlebars
103-
npm test
104-
```
94+
Before attempting the release Handlebars, please make sure that you have the following authorizations:
10595

106-
## Releasing the latest version
96+
- Push-access to `wycats/handlebars.js`
97+
- Publishing rights on npmjs.com for the `handlebars` package
98+
- Publishing rights on gemfury for the `handlebars-source` package
99+
- Push-access to the repo for legacy package managers: `components/handlebars`
100+
- Push-access to the production-repo of the handlebars site: `handlebars-lang/handlebarsjs.com-github-pages`
107101

108102
_When releasing a previous version of Handlebars, please look into the CONTRIBUNG.md in the corresponding branch._
109103

@@ -130,7 +124,13 @@ in those places still point to the latest version
130124
- [The AWS S3 Bucket](https://s3.amazonaws.com/builds.handlebarsjs.com) (check latest-tag)
131125
- [RubyGems](https://rubygems.org/gems/handlebars-source)
132126

133-
When everything is OK, the handlebars site needs to be updated to point to the new version numbers. The jsfiddle link should be updated to point to the most recent distribution for all instances in our documentation.
127+
When everything is OK, the **handlebars site** needs to be updated.
128+
129+
Go to the master branch of the repo [handlebars-lang/handlebarsjs.com-github-pages](https://github.com/handlebars-lang/handlebarsjs.com-github-pages/tree/master)
130+
and make a minimal change to the README. This will invoke a github-action that redeploys
131+
the site, fetching the latest version-number from the npm-registry.
132+
(note that the default-branch of this repo is not the master and regular changes are done
133+
in the `handlebars-lang/docs`-repo).
134134

135135
[generator-release]: https://github.com/walmartlabs/generator-release
136136
[pull-request]: https://github.com/wycats/handlebars.js/pull/new/master

0 commit comments

Comments
 (0)