Browse code

Document VERSION file update scheme

Signed-off-by: Arnaud Porterie <arnaud.porterie@docker.com>

Arnaud Porterie authored on 2015/03/23 10:45:01
Showing 1 changed files
... ...
@@ -364,7 +364,17 @@ echo "https://github.com/$GITHUBUSER/docker/compare/docker:master...$GITHUBUSER:
364 364
 Again, get two maintainers to validate, then merge, then push that pretty
365 365
 blue button to delete your branch.
366 366
 
367
-### 13. Rejoice and Evangelize!
367
+### 13. Update the API docs and VERSION files
368
+
369
+Now that version X.Y.Z is out, time to start working on the next! Update the
370
+content of the `VERSION` file to be the next minor (incrementing Y) and add the
371
+`-dev` suffix. For example, after 1.5.0 release, the `VERSION` file gets
372
+updated to `1.6.0-dev` (as in "1.6.0 in the making").
373
+
374
+Also create a new entry in `docs/sources/reference/api/` by copying the latest
375
+and bumping the version number (in both the file's name and content).
376
+
377
+### 14. Rejoice and Evangelize!
368 378
 
369 379
 Congratulations! You're done.
370 380