From owner-freebsd-current Sun Feb 22 15:07:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02792 for freebsd-current-outgoing; Sun, 22 Feb 1998 15:07:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02761 for ; Sun, 22 Feb 1998 15:07:32 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id QAA13851; Sun, 22 Feb 1998 16:07:20 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id QAA25719; Sun, 22 Feb 1998 16:07:18 -0700 Date: Sun, 22 Feb 1998 16:07:18 -0700 Message-Id: <199802222307.QAA25719@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Greg Lehey Cc: "Jordan K. Hubbard" , Nate Williams , Terry Lambert , current@FreeBSD.ORG Subject: Commit schedule (was Re: Terry, llamas, More breakage in -current...) In-Reply-To: <19980223084422.20994@freebie.lemis.com> References: <199802221752.KAA24429@mt.sri.com> <27525.888172295@time.cdrom.com> <19980223084422.20994@freebie.lemis.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Back to the original subject, guys. I proposed the following > > Let's accept the fact that -CURRENT's stability fluctuates and try > to influence the rhythm. One possiblity might be to say: > > - The first weekend in each month is the correct time for commiting > big modifications that can potentially compromise stability for a > while to come. What if the developer doesn't have time that weekend to commit code? What if that committer happens to have a project due that week, but two weeks after that they have time to hack on a solution, and answer questions on it? What then? > - Any Sunday is the correct time for commiting smaller modifications > that can potentially compromise stability for a few days. Why Sunday? I tend to be on business during the week, so Friday night/Saturday morning is the best time for me, since I can answer questions and fix bugs over the weekend. > The advantage is that people can expect -CURRENT to be relatively > stable on a Friday, and particularly stable at the end of a month. IMHO, this won't work simply because you can't dictate the schedule of a volunteer. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message