From cc0ac6ce2a5cb26e98aa93fdc3bfaaaa0f34b158 Mon Sep 17 00:00:00 2001 From: Peter Parente Date: Fri, 16 Oct 2015 22:06:08 -0400 Subject: [PATCH] Update README with starting SHA for new versioning --- README.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index ebecd7b8..c2953ca9 100644 --- a/README.md +++ b/README.md @@ -22,9 +22,11 @@ If this is your first time using Docker or any of the Jupyter projects, do the f ## Stacks, Tags, Versioning, and Progress -* Every folder here on GitHub has an equivalent `jupyter/stack` on Docker Hub. -* The `latest` tag in each Docker Hub repository tracks the `master` branch `HEAD` on GitHub. -* Additional 12-character tags on Docker Hub refer to git commit SHAs on **GitHub**. +Starting with [git commit SHA 9bd33dcc8688](https://github.com/jupyter/docker-stacks/tree/9bd33dcc8688): + +* Every folder here on GitHub has an equivalent `jupyter/` on Docker Hub. +* The `latest` tag in each Docker Hub repository tracks the `master` branch `HEAD` reference on GitHub. +* Any 12-character image tag on Docker Hub refers to a git commit SHA here on GitHub. * Stack contents (e.g., new library versions) will be updated upon request via PRs against this project. * Users looking to remain on older builds should refer to specific git SHA tagged images in their work, not `latest`. * Users who want to know the contents of a specific tagged image on Docker Hub can take its tag and use it as a git SHA to inspect the state of this repo at the time of that image build.