From ea1ab48e81b440da53b9ae7aae0312acd94423e2 Mon Sep 17 00:00:00 2001
From: Dane Springmeyer <dane@dbsgeo.com>
Date: Fri, 25 Oct 2013 11:45:00 -0700
Subject: [PATCH] Updated MapnikReleaseSteps (markdown)

---
 MapnikReleaseSteps.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/MapnikReleaseSteps.md b/MapnikReleaseSteps.md
index 3b00e22..02a95be 100644
--- a/MapnikReleaseSteps.md
+++ b/MapnikReleaseSteps.md
@@ -132,6 +132,8 @@ cd ${MAPNIK_SOURCES}
 
 ### Post tag updates
 
+* Create a new `mapnik-reference` entry for the release: https://github.com/mapnik/mapnik-reference
+
 * Update master branches entries in [CHANGELOG](https://github.com/mapnik/mapnik/blob/master/CHANGELOG.md) from the new release (if relevant, e.g. if you are tagging and releasing a stable release not from the master branch).
 
 If this was a major release and a stable series is likely, now branch it, for example a `2.1.0` release would warrant an immediate `2.1.x` branch for a stable series of bugfix releases.