Date: Thu, 11 Aug 2011 12:45:23 +0100 From: Howard Jones <howie@thingy.com> To: freebsd-questions@freebsd.org Subject: Re: [freebsd-questions] FreeBSD supported versions (UNCLASSIFIED) Message-ID: <4E43C0D3.6040105@thingy.com> In-Reply-To: <F1DF92842F3E008A2B4C9F69@mac-pro.magehandbook.com> References: <55A74C53CF85244A8000286B9B0313FE19534CB154@SCHOENTB1EXMB02.ap.ds.army.mil> <46F365E4DFD3421A4869B342@mac-pro.magehandbook.com> <CAHu1Y72BvzSWvn4Vpqf6BmG-CEexh6c4tDB8s3vZLWr7r40tfw@mail.gmail.com> <F1DF92842F3E008A2B4C9F69@mac-pro.magehandbook.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/08/2011 12:37, Daniel Staal wrote: > > (Well, ok, given the current release structure having an update today > means you are in a supported branch, and that supported branch will > continue to get updates for the foreseeable future. But that still > does not tell me when the branch is likely to get unsupported, and in > theory a patch release could be made on the last day of support for a > branch.) A simple solution would be for there to ALWAYS be a patch release on the last day of support for a branch, that creates /etc/NOT-SUPPORTED or similar. Then it's just a matter of adding an /etc/cron.daily job to report on that, as long as you are following updates (and if you aren't you don't care about this issue). I can't think of any other OS that does this, either - they generally just report that there are no available updates. Howie
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E43C0D3.6040105>