Return-Path: Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 87725 invoked from network); 20 Jan 2000 02:11:29 -0000 Received: from mail1.sirius.com (205.134.253.131) by 63.211.145.10 with SMTP; 20 Jan 2000 02:11:29 -0000 Received: from isdn-chakotay (46-78-127-216.ip.sirius.com [216.127.78.46]) by mail1.sirius.com (8.9.3/8.9.1) with SMTP id SAA79665 for ; Wed, 19 Jan 2000 18:11:22 -0800 (PST) Sender: jhunter@sirius.com Message-ID: <38866DFA.446B@acm.org> Date: Wed, 19 Jan 2000 18:07:54 -0800 From: Jason Hunter X-Mailer: Mozilla 3.03C-SGI (X11; I; IRIX 6.2 IP22) MIME-Version: 1.0 To: tomcat-dev@jakarta.apache.org Subject: Re: Are "burn-in" periods really required for milestone drops? References: <8525686B.005D59CA.00@d54mta04.raleigh.ibm.com> <3886014D.AA2AEE1E@gefionsoftware.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hans Bergsten wrote: > I agree; burn in for milestones seems like overkill and slows down > the process. My suggestion is to drop them, but keep the burn in for > the final release. The answer to this depends mostly on what quality people expect from milestones. People probably expect Mn to be better than M(n-1). If that's true, then we need some burn-in so we can be sure that the check-in done right before the milestone snap didn't break something big. Plus, if people appear willing to do a little testing of the proposed milestone and give good feedback (as Sam says has happened), then that's reason enough to keep the burn-in. Tomcat needs all the testing it can get! If we can do a milestone on its own branch and continue checking in to the root, then there's not much harm in having burn-in. -jh- -- Jason Hunter jhunter@acm.org Book: http://www.servlets.com/book 2.0 to 2.1: http://www.javaworld.com/jw-12-1998/jw-12-servletapi.html 2.1 to 2.2: http://www.javaworld.com/jw-10-1999/jw-10-servletapi.html