Date: Fri, 23 Dec 2005 02:34:43 -0800 From: Colin Percival <cperciva@freebsd.org> To: Brian Candler <B.Candler@pobox.com> Cc: Jo Rhett <jrhett@svcolo.com>, stable@freebsd.org, current <current@freebsd.org>, "Matthew D. Fuller" <fullermd@over-yonder.net> Subject: Re: Fast releases demand binary updates.. (Was: Release schedule for 2006) Message-ID: <43ABD2C3.9020301@freebsd.org> In-Reply-To: <20051223100251.GB6049@uk.tiscali.com> References: <43A266E5.3080103@samsco.org> <20051217220021.GB93998@svcolo.com> <20051218023725.GM63497@over-yonder.net> <20051222210904.GH39174@svcolo.com> <20051223030813.GD63497@over-yonder.net> <20051223100251.GB6049@uk.tiscali.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Candler wrote: > I think the real concern here is: for how long after RELEASE_X_Y are binary > patches for it made available? I build FreeBSD Update patches for all the branches supported by the FreeBSD Security Team. To answer a couple of other questions: FreeBSD Update is something which I _personally_ support; it isn't supported by the _project_, because at the moment there isn't anyone else who could take over running it if I get hit by a bus. Re the long list of requests people have made (starting with "amd64 support" and "make this officially supported by the project"), I'll get to those as soon as I have time. Sadly, I have a pesky thing called "a full time job" and my FreeBSD time has been occupied with portsnap lately. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43ABD2C3.9020301>