From owner-freebsd-current Tue Jun 20 11:35: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id ECF2A37BF17 for ; Tue, 20 Jun 2000 11:34:56 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA41016; Tue, 20 Jun 2000 12:34:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA70626; Tue, 20 Jun 2000 12:33:21 -0600 (MDT) Message-Id: <200006201833.MAA70626@harmony.village.org> To: Jason Evans Subject: Re: HEADS UP: Destabilization due to SMP development Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 19 Jun 2000 11:53:30 PDT." <20000619115330.D79318@blitz.canonware.com> References: <20000619115330.D79318@blitz.canonware.com> Date: Tue, 20 Jun 2000 12:33:21 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000619115330.D79318@blitz.canonware.com> Jason Evans writes: : Summary: -current will be destabilized for an extended period (on the order : of months). A tag (not a branch) will be laid down before the initial : checkin, and non-developers should either stick closely to that tag until : the kernel stabilizes, or expect large doses of pain. This tag will be : laid down as soon as June 26, 00:00 PST, with a minimum 24 hour warning : beforehand. Thanks for the fair warning. Now don't do it. Has core approved this? I don't think so, I've seen nothign from them about it. The instability ni -current for MONTHS is pain not acceptible. We've never really allowed that in the past. A CVS branch would be mcuh better for this sort of thing. I know that's a pain as well, but this is just for SMP people and the rest of us shouldn't have to deal with the pain. I understand your desire to have it all in a working tree, but causing pain for ALL developers for potentially MONTHS isn't a reasonable request. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message