From 5092a3bb324cc04c403f006764e218966e280313 Mon Sep 17 00:00:00 2001
From: "David I. Lehn" <dlehn@users.sourceforge.net>
Date: Wed, 9 Jan 2002 04:50:13 +0000
Subject: [PATCH] Start of a release checklist and policies

Original commit message from CVS:
Start of a release checklist and policies
---
 docs/random/release | 56 +++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 56 insertions(+)
 create mode 100644 docs/random/release

diff --git a/docs/random/release b/docs/random/release
new file mode 100644
index 0000000000..6b5263d072
--- /dev/null
+++ b/docs/random/release
@@ -0,0 +1,56 @@
+Release TODO
+------------
+
+* make distcheck should pass
+
+* test suite should pass
+
+* autotools have latest config.{guess,sub}
+  This is needed in order to support newer platforms.
+  On Debian install the autotools-dev package to get these.
+
+* depending on how the API has changed update the libtool versioning
+  in configure.ac.  Look at the libtool info page about versioning for
+  guidelines.
+
+* update package version
+
+* tag tree
+  http://gstreamer.net/dev/cvs.php
+  add tag to above page
+
+* update web site release notes
+
+* update web site news items for release
+
+* upload to sourceforge
+
+* announce to:
+  freshmeat
+  gstreamer-{devel, announce}
+  linux-audio-dev (?)
+  gnome lists (?)
+  lwn (if it's a big release)
+
+
+Should work:
+
+* autoconf feature to allow building outside source dir
+
+
+
+Package version policy
+----------------------
+
+Use major.minor.micro versioning
+
+Before 1.0.0
+
+Update micro until code and API are fairly stable, then update minor.
+
+
+After 1.0.0
+
+Update major when code and api hit new level of stability or major features.
+Update minor on API changes.
+Update micro on API-compatible changes.