Hi Henrik & Doug, At 02.21 06/05/2006, Henrik Nordstrom wrote:
lör 2006-05-06 klockan 12:08 +1200 skrev Doug Dixon: > Option 1 - severity based > We release PRE4 when all the criticals and blockers have been fixed. Over optimistic. This is the quality level required for a RC/STABLE release. > Option 2 - hand-picked > We hand pick a fixed list of bugs which we think we can fix within a > reasonably short time. We release when they are all fixed. No other > bugs can enter the list once it is picked. > > Option 3 - time based > We release PRE4 on June 1, and fix whatever bugs we can until then > (blockers first). Combination of 2 & 3 is my vote. Start with a hand picked list and a target date. Adjust the list over time, removing items found to not be realistic for the target date and add items which is found sufficiently important, and if necessary to preserve reasonable faith in the release adjust the time (limited +1 week or so, no limit on early release when goals met). This is a scaled down version of the process currently used for the STABLE releases. Regards Henrik
I fully agree with the Henrik's vote. Regards Guido - ======================================================== Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
