commit 624c68daa1a30df6d81976553da608b6152a5b83
author Dave Cheney <dave@cheney.net> Tue Sep 15 17:05:23 2015 +1000
committer Dave Cheney <dave@cheney.net> Tue Sep 15 07:16:00 2015 +0000
tree 9ac387ed8a0129281fc6e1b653f81f47ad960ff3
parent bb4c56b7fea11a0cfd694b97137801e9fe73c642

design: release proposal draft iv

Updates golang/go#12302

Only a few small nits

- fix markdown formatting in implementation section.
- poetically, the name of the debian package with the unsable git hash
  has changed, so link to a hopefully more stable url.

Change-Id: I5809a62080e5c7ed529e912ad8845f0ce5731d0c
Reviewed-on: https://go-review.googlesource.com/14578
Reviewed-by: Andrew Gerrand <adg@golang.org>

design/12302-release-proposal.md

diff --git a/design/12302-release-proposal.md b/design/12302-release-proposal.md
index b743fa1..5a9fb6c 100644
--- a/design/12302-release-proposal.md
+++ b/design/12302-release-proposal.md
@@ -2,7 +2,7 @@
 
 Author: Dave Cheney <dave@cheney.net>
 
-Last updated: 8 September 2015
+Last updated: 15 September 2015
 
 ## Abstract
 
@@ -74,7 +74,7 @@
 Additionally, operating system distributors such as Debian and Ubuntu strongly
 prefer to package released versions of a library or application, and are
 currently reduced to
-[doing things like this](https://ftp-master.debian.org/new/golang-github-odeke-em-command_0.0~git20150727.0.cf17ee2-1.html).
+[doing things like this](https://packages.debian.org/stretch/golang-github-odeke-em-command-dev).
 
 In the spirit of doing less and enabling more, this proposal establishes the
 minimum required for humans and tools to identify released versions by inspecting
@@ -154,12 +154,12 @@
 
 Authors of Go libraries should follow these two maxims:
 
-# Packages which are the same, must share the same import path. This proposal
-  provides the mechanism for consumers to identify a specific release version
-  without the requirement to encode that information in the import path.
-# Packages which are not the same, must not have the same import path. A clone or
-  fork of a library or project is not the same as its parent, so it should have
-  a new name -- a new import path.
+1. Packages which are the same, must share the same import path. This proposal
+   provides the mechanism for consumers to identify a specific release version
+   without the requirement to encode that information in the import path.
+2. Packages which are not the same, must not have the same import path. A clone or
+   fork of a library or project is not the same as its parent, so it should have
+   a new name -- a new import path.
 
 ## Implementation