From owner-freebsd-hackers@FreeBSD.ORG Fri Jun 15 18:37:37 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (unknown [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 53A7A1065670 for ; Fri, 15 Jun 2012 18:37:37 +0000 (UTC) (envelope-from nonesuch@longcount.org) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id BBD868FC0C for ; Fri, 15 Jun 2012 18:37:36 +0000 (UTC) Received: by lbon10 with SMTP id n10so3782092lbo.13 for ; Fri, 15 Jun 2012 11:37:30 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding :x-gm-message-state; bh=zBOAy6M0MhzZ05/gTavYli70vCjUzEZZVh+5flgH5Ow=; b=B+UJZyEq8yerY9EAHiwpRQ/lMvMUN+X2LYrDNSYWY4XvJ0MTMcrk0//0J1P+7GWq6y PLWgl83rRNQgeudjiwa47tOApuJDPGOiYt20DCjek7q+D+G3W8peqvtajrIGfYgI1cf3 9diwoB5is24rG1om8nOXrmTQK8QJgLXsAsW5KPT/BaT4Hy9eK25iWXx1tsrjV9ON4T4m w61Nk1ql3HAekhEOfRTyaeMr32C/1hXbQdyOHJbJSNYY9040127P/1yLzU2Lhb+TiAgP BkcJA5UMtOZ/114JiJdbD0+sFp4ybkOWZfjxIwbrb57sYeVTJUouEyMgqKyjtShYgSsf n34A== MIME-Version: 1.0 Received: by 10.152.103.109 with SMTP id fv13mr6421328lab.33.1339785449943; Fri, 15 Jun 2012 11:37:29 -0700 (PDT) Received: by 10.112.27.137 with HTTP; Fri, 15 Jun 2012 11:37:29 -0700 (PDT) X-Originating-IP: [216.223.13.198] In-Reply-To: References: <4FD9A0E2.9010101@my.gd> Date: Fri, 15 Jun 2012 14:37:29 -0400 Message-ID: From: Mark Saad To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQn9jidI0yRNZNQNuBZhNBsaqENblsg0cWlezCs18sxZR62kkKZRrQ2Vc1P6PImbbv/p+QCQ Subject: Re: Upcoming release schedule - 8.4 ? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 18:37:37 -0000 So what , this fell on deaf ears or was it a horridly bad idea ? Anyone care to share ? On Thu, Jun 14, 2012 at 5:12 PM, Mark Saad wrote: > All > =C2=A0I have an partial solution to this issue I was thinking about this = on > my morning train ride, so its a bit bumpy. > > Here are my solutions they are not complete but I think its a good start. > > 1. When official errata and security updates hit the tree . Providing > updated install media could be step one . Maybe rebuild install media > periodical say every 3 months, if it warrants it. > > 2. Change FreeBSD-update to allow you to select what updates you want, > and make it work for stable. Simply put think "freebsd-update fetch > stable kernel" or " freebsd-update fetch release base" > > 3. Change FreeBSD-update =C2=A0to tweak a library so the -pN level is not > hardcoded into the kernel at compile time. Currently FreeBSD's patch > or "p level -pN " is a newvers.sh function . > > 4. Publish a longer time line for future releases and make it easier > to find. =C2=A0While ken smith's email about the 9.1-RELEASE time line wa= s > a good start , for 9.1,I feel that a short general time line on > http://www.freebsd.org/releases/ would do a world of good for people > want to know whats up next and when can I expect it. It does not need > to be exact just a rough estimate. > > The sum total of all of this , in my eyes, is when updated drivers ( I > know its a still a wish and not reality ) , bug fixes , security > updates are released , new installs done around that time will start > out with all of the good bits. Secondly when new updates are released > users can apply base updates and kernel updates to both release and > stable as needed. Lastly updates released via this new method would be > easily checked via uname -a =C2=A0or maybe " freebsd-update show version" > > > Fire away. > > --- > =C2=A0Mark Saad | mark.saad@longcount.org --=20 mark saad | nonesuch@longcount.org