Skip to content

Commit 964123e

Browse files
authored
Add a "maintainers" section to the README
1 parent 2800fe4 commit 964123e

File tree

1 file changed

+7
-0
lines changed

1 file changed

+7
-0
lines changed

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,3 +29,10 @@ The Calendar might nag you for a Google Calendar API key. You can either ask som
2929

3030
## Contributing
3131
Please see [CONTRIBUTING](CONTRIBUTING.md)
32+
33+
## Maintainers
34+
Before you release a new version to the app store, you'll want to use the `npm version` command. That will automatically bump the version numbers and tag the commit.
35+
36+
You should use Release Candidates generously – do, for example, `npm version 2.2.0-rc.1`, then make sure it builds, and run it on the simulators / devices / whatever you would do before you upload it to iTunes Connect / the Play Store. Then, once it's passed all your manual checks, you can do `npm version 2.2.0`, and build that commit, because the only thing that will have changed is the numbers. That way, if something goes wrong while you're testing it, you can do 2.2.0-rc.2, instead of … having 2.0.0-rc.2 be _newer_ than 2.0.0 (final).
37+
38+
Anyway. TL;DR: `npm version` is your friend! Use it.

0 commit comments

Comments
 (0)