WIP: Add a docs/branching.md doc with info on specialized branch pointer moving.

Also clarify this repo further in docs/releasing.md.
And fix some other related doc issues.

Author: david-mcmahon

README.md

@@ -82,7 +82,7 @@ your favorite editor.
 ### Tools
 
 * [mailer](https://github.com/kubernetes/release/blob/master/mailer) : Generic mail interface (due to Google's deprecation of sendmail)
-* [find_green_job](https://github.com/kubernetes/release/blob/master/find_green_job) : Ask Jenkins for a good build to use
+* [find_green_build](https://github.com/kubernetes/release/blob/master/find_green_build) : Ask Jenkins for a good build to use
 * [script-template](https://github.com/kubernetes/release/blob/master/script-template) : Generate a script template in the kubernetes/release ecosystem
 * [relnotes](https://github.com/kubernetes/release/blob/master/relnotes) : Scrape github for release notes \(See below for more info\)
 

docs/branching.md

@@ -0,0 +1,33 @@
+# Branching
+
+Some caveats to branching.
+
+We usually branch early as a psychological placeholder to keep a cap on
+changes landing on master.
+
+During that time only milestone-specific changes are allowed into the
+master and when things are stable (enough) we effectively move the
+release branch to the HEAD of the master branch:
+
+```
+# checkout a local branch
+$ git checkout -b release-1.3 upstream/release-1.3
+# move the pointer to top of master branch
+$ git reset --hard upstream/master
+# Redo the branching activities
+$ #do anago::rev_version_base() again (and commit it)
+$ build/versionize-docs.sh v1.3.0-beta.0 (and commit)
+$ git tag -f v1.3.0-beta.0
+# Finally push it upstream (or whatever remote you are using)
+$ git push -f upstream release-1.3:release-1.3.
+```
+
+** Like everything else, this should be scripted into a well documented,
+error-checked button (script) so it can just be logically handled by
+anyone with minimal inputs.
+
+
+
+Once that happens we then open up master to milestone+1 changes
+and move to the 2 phase cherry-pick model:
+

docs/releasing.md

@@ -1,6 +1,19 @@
 # Kubernetes Releases
 
-TBD
+This repo contains the tooling and documentation for the release of
+the core Kubernetes project.  
+
+In the future it is expected that the functionality will expand and be
+generalized to support release infrastrcture for all of the kubernetes
+sub-projects as well.
+
+The tooling and doc here is expected to change often as requirements
+change and the project(s) evolve.
+
+The doc and tooling in this repo is NOT designed to address the planning,
+coordination of releases.  See ---insert goltermann and PM project
+planning docs/links here----.
+
 
 ## Types of Releases