From 61ecd58e11defed7d2992aeab01b797b62d1a86c Mon Sep 17 00:00:00 2001 From: Henning Geinitz Date: Thu, 26 Sep 2002 21:47:20 +0000 Subject: [PATCH] Added paragraph about the different freeze types and a timetable. --- doc/releases.txt | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/doc/releases.txt b/doc/releases.txt index 7200780ff..e65e8f850 100644 --- a/doc/releases.txt +++ b/doc/releases.txt @@ -1,7 +1,17 @@ -2002-03-17 +2002-09-26 This text summarizes some points to pay attention to when a new realease -of sane-backends should be made. +of sane-backends should is planned. + +Timetable (approximate periods): + +Day 0: Announcement of upcomming 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 + compilation problems or render a backend completely unusable, and + documentation updates are allowed) +Day 42: Release Before the release: