From owner-freebsd-current Sun Dec 8 15:32:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA29876 for current-outgoing; Sun, 8 Dec 1996 15:32:39 -0800 (PST) Received: from icicle.winternet.com (adm@icicle.winternet.com [198.174.169.5]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA29868 for ; Sun, 8 Dec 1996 15:32:36 -0800 (PST) Received: (from adm@localhost) by icicle.winternet.com (8.7.5/8.7.5) id RAA03403 for ; Sun, 8 Dec 1996 17:32:33 -0600 (CST) Posted-Date: Sun, 8 Dec 1996 17:32:33 -0600 (CST) Received: from ppp-67-42.dialup.winternet.com(204.246.67.42) by icicle.winternet.com via smap (V2.0beta) id xma003387; Sun, 8 Dec 96 17:32:21 -0600 Date: Sun, 8 Dec 1996 17:31:25 -0600 () From: Jimbo Bahooli To: freebsd-current@freebsd.org Subject: Possible solution to upgrade problems... Message-ID: X-X-Sender: moke@icicle.winternet.com MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I do not know if this has already been suggested, or what not but here it goes. I would suggest something like the ports section for upgrades to -RELEASE systems. That way the branch could die but relevant fixes could still be released. A possible setup would be like this, lets say 2.2-RELEASE comes out and is bundled with sendmail 8.8.10. Yet three days later there is a bug found in it. Any 2.2-RELEASE user could then go to /pub/FreeBSD/upgrades-2.2/sendmail download it, it would be similar to a port in structure, then just make it.