From 21840be6f14351a46535319d6517776445a17e0d Mon Sep 17 00:00:00 2001 From: Henning Geinitz Date: Sun, 7 Nov 2004 19:40:52 +0000 Subject: [PATCH] Updated according to current practice. --- ChangeLog | 1 + doc/releases.txt | 32 +++++++++++++++++++------------- 2 files changed, 20 insertions(+), 13 deletions(-) diff --git a/ChangeLog b/ChangeLog index e9c5f9584..38aa9d760 100644 --- a/ChangeLog +++ b/ChangeLog @@ -2,5 +2,6 @@ * configure configure.in: Updated version. Enabled compilation warnings. + * doc/releases.txt: Updated according to current practice. Older entries can be found in ChangeLog-1.0.15. diff --git a/doc/releases.txt b/doc/releases.txt index bac0e7a9a..e9ab69ce2 100644 --- a/doc/releases.txt +++ b/doc/releases.txt @@ -1,4 +1,4 @@ -2003-11-26 +2004-11-07 This text summarizes some points to pay attention to when a new release of sane-backends should is planned. @@ -6,17 +6,16 @@ of sane-backends should is planned. Timetable (approximate periods): Day 0: Announcement of upcoming release on sane-devel including timetable -Day 14: Backend freeze (no new backends are allowed to enter the distribution) -Day 21: Feature freeze (only bugfixes + documentation updates) -Day 35: Code freeze (only fixes for bugs that can destroy hardware, can cause +Day 14: Feature freeze (only bugfixes + documentation updates) +Day 28: Code freeze (only fixes for bugs that can destroy hardware, can cause compilation problems or render a backend completely unusable, and documentation updates are allowed) -Day 42: Release +Day 35: Release Before the release: * Make sure that config.guess and config.sub are up-to-date (get them from - ftp://ftp.gnu.org/pub/gnu/config/). + the latest autoconf release). * configure.in: increase version number (twice!) * configure.in: remove -cvs from textual version number * configure.in: set is_release=no @@ -24,24 +23,31 @@ Before the release: * NEWS: update and enter date of release * sane-backends.lsm: update * ChangeLog: set release marker -* final compilation test -* tag CVS with release tag; e.g.: 'cvs tag RELEASE_1_0_4' -* make diff from last release; - e.g.: 'cvs diff -uNr RELEASE_1_0_12 > sane-backends-1.0.12-1.0.13.diff' +* tag CVS with release tag; e.g.: 'cvs tag RELEASE_1_0_15' Making the release: * make tar.gz, sane-backends-x.y.z.lsm, and .md5sum with "make sane-backends" -* upload these files together with the .diff to the FTP server -* update sane-backends.html and sane-mfgs.html on sane-project.org +* unpack tar.gz in temporary directory +* make diff from last release by unpacking it also in temporary directory + and running e.g. + diff -uNr sane-backends-1.0.14 sane-backends-1.0.15 > sane-backends-1.0.14-1.0.15.diff' +* check that the diff applies cleanly to the old version +* check that the new version .tar.gz can be compiled +* upload these files together with the .diff to the FTP/HTTP servers + (at the moment: rpm.org and alioth.debian.org). +* copy sane-backends.html to sane-backends-"old-version".html, + update sane-backends.html, sane-mfgs.html and sane-supported-deviced.html + on sane-project.org * update SANE standard and man pages on sane-project.org * check and update platforms page on sane-project.org * write announcements on sane-project.org and sane-devel, maybe others (e.g. freshmeat), include the md5 hash -* upload to mirrors that don't get the files automatically (sunsite) +* upload to mirrors that don't get the files automatically (ibiblio.org) After the release: +* move ChangeLog to ChangeLog-"version" and start a new ChangeLog * configure.in: add -cvs suffix * configure.in: set is_release=no * configure: regenerate