Date: Tue, 3 Oct 2000 17:43:13 -0700 From: Alfred Perlstein <bright@wintelcom.net> To: Jordan Hubbard <jkh@winston.osd.bsdi.com> Cc: Paul Richards <paul@originative.co.uk>, Christopher Masto <chris@netmonger.net>, Warner Losh <imp@village.org>, Kris Kennaway <kris@FreeBSD.org>, Joseph Scott <joseph.scott@owp.csus.edu>, Brian Somers <brian@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org, freebsd-security@FreeBSD.org Subject: Re: How long for -stable [ Re: cvs commit: src/usr.bin/finger finger.c ] Message-ID: <20001003174313.U27736@fw.wintelcom.net> In-Reply-To: <84222.970618959@winston.osd.bsdi.com>; from jkh@winston.osd.bsdi.com on Tue, Oct 03, 2000 at 05:22:39PM -0700 References: <paul@originative.co.uk> <84222.970618959@winston.osd.bsdi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Jordan Hubbard <jkh@winston.osd.bsdi.com> [001003 17:23] wrote: > > We could also look into providing an "update" command or something > which would pull either sources or binaries over from a snapshot box > and make the process of getting up to the branch-head a lot easier. > It's long been on my wishlist and I'm at the point where I'd be > willing to devote some BSDi resources to both writing the software > and setting up a build box for creating the relevant binaries on an > ongoing basis. You ought to go to the cube next to you, Mike Smith said he had something along the lines of that, er, something that would generate a binary delta that could be spammed over an existing install. > This would seem to me to give us the best of all possible worlds. > That portion of our customer base which wants a truly moribund -stable > with just security enhancements and "by special request" fixes could > have that by lagging back a branch. The other portion which wants a > more active -stable could subscribe to the most current -stable. The > final remaining portion which enjoys watching their blood come out in > arterial spurts could subscribe to -current. :) > > What say? I think supporting back to 3.x is a good idea. It's pretty harsh to be telling users to bugger off when we've only just released 4.0 6 months ago and they're stuck with 3.x. I'd love to see a couple of committers come on board with the explicit job of backporting important fixes, perhaps in passing people interested in the project we could offer a backporting position as a starter or full time post sort of like the ports team. Might I suggest it'd be pretty helpful to have a couple of speedy 3.x (and probably 4.x) boxes set up some place with console access to make these types of fixes easier for our developers lacking in hardware resources. Running them off a private net behind freefall would work pretty well no? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001003174313.U27736>