From owner-freebsd-questions@freebsd.org Fri May 11 14:41:12 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BAFCAFD7FD0 for ; Fri, 11 May 2018 14:41:12 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from forward105o.mail.yandex.net (forward105o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::608]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1565675B49 for ; Fri, 11 May 2018 14:41:11 +0000 (UTC) (envelope-from jude.obscure@yandex.com) Received: from mxback5o.mail.yandex.net (mxback5o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::1f]) by forward105o.mail.yandex.net (Yandex) with ESMTP id 2A558444779D; Fri, 11 May 2018 17:41:09 +0300 (MSK) Received: from smtp1j.mail.yandex.net (smtp1j.mail.yandex.net [2a02:6b8:0:801::ab]) by mxback5o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id bNO3gFVluY-f8M81c7V; Fri, 11 May 2018 17:41:09 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1526049669; bh=nedFk6LlsCM9vt1nln3d/S0g7En37oFg5eL5Zehb7+w=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=wip+K/ZYM0xdx7snVM0zc7TMbkpmoBfkzxLdgmrMeoMwvJWvKONCx2BWTVeXdwlcy FoL+E1aVIq1URMOZrd518jxFXlUCqR6AQMbq1A3rnt0L37nJuTPoh8f6VblmGgMDPi fYvYOKxV5oOJqWanG/8jqDmtyJaPT9UaFosG3xOM= Received: by smtp1j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id oyIdro3KDz-f5P8pYdp; Fri, 11 May 2018 17:41:06 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.com; s=mail; t=1526049667; bh=nedFk6LlsCM9vt1nln3d/S0g7En37oFg5eL5Zehb7+w=; h=Subject:To:Cc:References:From:Message-ID:Date:In-Reply-To; b=EMMsjtuoUQ7sPmhiOP/lR4tJHfldIVyf6KcqaJspQ/yv8hMU7PhB2zrEoYAh67W8b 7mwUG7vugZGTjoC64td5Neoji8OsSaVi3l8HVEKmNUh7PHnQdINb7GxxATkLtaKtu/ b8cvdZTctngbI5G5SRUlXhA2TR1l5sfpJ1eSBRnk= Authentication-Results: smtp1j.mail.yandex.net; dkim=pass header.i=@yandex.com Subject: Re: A request for release engineering To: Robroy Gregg , Kristof Provost Cc: Arthur Chance , freebsd-questions@freebsd.org References: <4acac175-9bf2-40a6-a41a-cb5870641c8d@yandex.com> <670715be-849c-47fc-72b4-42b81cf31c0a@qeng-ho.org> From: Manish Jain Message-ID: <0fbe4e76-f482-c936-7bf2-2b689d6902d2@yandex.com> Date: Fri, 11 May 2018 20:10:14 +0530 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2018 14:41:13 -0000 On 05/11/18 19:45, Robroy Gregg wrote: > > On Fri, 11 May 2018, Kristof Provost wrote: > >> On 11 May 2018, at 9:11, Arthur Chance wrote: >>> On 10/05/2018 19:15, Manish Jain wrote: >>>> Hi, >>>> >>>> I have no idea whether this is the right list to make this request to. >>>> But I could not find any other list that would definitely be better >>>> suited. >>>> >>>> I noticed when trying to build a port under my 10.3 box that support >>>> for >>>> 10.3 has now expired. I have no problems with that - I will install 12 >>>> afresh when it becomes available later this year. >>>> >>>> But since installing afresh demands a whole effort, I request that >>>> FreeBSD reduce its new releases to one per year, while the support >>>> period is increased to 3 years per release. >>>> >>>> Does this sound like a good request to others too ? >>>> >>> >>> The FreeBSD support model was announced over three years ago: >>> >>> >> https://lists.freebsd.org/pipermail/freebsd-announce/2015-February/001624.html >> >>> >>> In particular >>> >>> - Each new release from the stable/X branch deprecates the previous >>>   release on the branch, providing a three-month window within which >>>   consumers are urged to upgrade to the latest release.  During this >>>   three-month window, Security Advisories and Errata Notices will still >>>   be issued for the previous release, as necessary. >>> >>> Why not simply update to 10.4? >>> >> FreeBSD 10.4 reaches end-of-life on October 31, 2018. At this point >> I?d recommend an upgrade to 11.1 right now, to get to a supported >> version and then an upgrade to 11.2 within three months of the release >> of 11.2. > > I wonder how many other people are like me--planning to "float" from > 10.3-RELEASE to 11.2-RELEASE on some computers, just to face the devil > once instead of twice (the devil to which I refer's the one who's "in > the details" every time I change anything on a server). There is one point on which I request expert advice. Since bumping the version up using freebsd-update needs you to install all packages afresh, it would appear to my naked eye that it never makes sense to upgrade. Instead, one should simply wait till one's release version goes beyond EOL - and then install the latest available release afresh. This is just what I plan on this box (10.3) - wait till November, and then install 12 over the current installation. Exactly when does the upgrade via freebsd-update bring any real advantage to the user ? I see one disadvantage in upgrading - things don't work as smoothly/reliably as with a fresh installation. -- Tx and Regards, Manish Jain