From owner-freebsd-hackers@FreeBSD.ORG Thu Jun 14 21:12:48 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8CB36106564A for ; Thu, 14 Jun 2012 21:12:48 +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 0A7828FC08 for ; Thu, 14 Jun 2012 21:12:47 +0000 (UTC) Received: by lbon10 with SMTP id n10so2958356lbo.13 for ; Thu, 14 Jun 2012 14:12:46 -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:x-gm-message-state; bh=rQ4YappFH5BmLXJMIexYlfo66mRmvyDw2ObzV1F51b8=; b=mbnphzt1+YjOUUPvTTu9mf5vHjYSDgSiaysndhLAYtMdUJkBfFrBZMv8ZW/f6uXDUn cSy5R1z1xDMP35P6f8CisWXaWLuajlwBP2cIsWJdRyQWmTITQPsDSQi1XvU5X6rs3Tb8 DazxF3hEbPY4ynkHjfHJKBl7B5vkVTqP8AeY/GHk3C8eQMKwCha/JMWusSX5+3fPbZcg Z+A/QOIuJtkouIDrXDMcfa7BNk2Mk4lB/0smgUp0PWKa+ttONvy/ZDLjeiz/eYaN1DCT AgK81WbsJtfAme7gWsIwUtRzdxH239DvBoqTa3MNb9q2UOm7Rrym23hFhjgclw4rjRmU T+Qw== MIME-Version: 1.0 Received: by 10.112.29.131 with SMTP id k3mr1600335lbh.53.1339708366720; Thu, 14 Jun 2012 14:12:46 -0700 (PDT) Received: by 10.112.27.137 with HTTP; Thu, 14 Jun 2012 14:12:46 -0700 (PDT) X-Originating-IP: [216.223.13.198] In-Reply-To: References: <4FD9A0E2.9010101@my.gd> Date: Thu, 14 Jun 2012 17:12:46 -0400 Message-ID: From: Mark Saad To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQnKtBw9ZSlF3F4xwHNfXt9J990fZTegO0mDOesYU8Vk3A5jrKIJplR7waBp1c5E1Hy0dz2g 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: Thu, 14 Jun 2012 21:12:48 -0000 All I 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 to 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. While ken smith's email about the 9.1-RELEASE time line was 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 or maybe " freebsd-update show version" Fire away. --- Mark Saad | mark.saad@longcount.org