Date: Wed, 17 Sep 2008 15:02:07 -0700 From: Jo Rhett <jrhett@netconsonance.com> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-stable <freebsd-stable@FreeBSD.org>, Wesley Shields <wxs@FreeBSD.org>, Nathan Way <nathan@datanode.com>, Ben Kaduk <minimarmot@gmail.com> Subject: Re: Upcoming Releases Schedule... Message-ID: <0C2C7E9B-61E3-4720-B76F-4745A3C963DA@netconsonance.com> In-Reply-To: <alpine.BSF.1.10.0809162043380.64176@fledge.watson.org> References: <1219409496.10487.22.camel@bauer.cse.buffalo.edu> <593618A3-56DA-4891-A4A0-690E9A9C5B32@netconsonance.com> <F17BE4F1F989BB4A81EB94C36712A9736F3493@dni-mail.datanode.com> <20080904133604.GB1188@atarininja.org> <CB36FE28-D125-4C22-B5DE-1001515DD8A6@netconsonance.com> <47d0403c0809051319r3c82f87bhdb15ce5b0167987a@mail.gmail.com> <alpine.BSF.1.10.0809061159410.28840@fledge.watson.org> <2742CAB1-8FF2-425D-A3B6-0658D7DB8F4D@netconsonance.com> <alpine.BSF.1.10.0809162043380.64176@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Mon, 15 Sep 2008, Jo Rhett wrote: >> Robert, I'd like to point out to you that when I complained about >> 6.2's accelerated EoL, I was soundly boxed around the ears and told >> that I should have been paying attention to the projected EoL date >> when we decided to roll out 6.2 across the business. >> >> Now you are saying that expected EoL will be determined at some >> random point in the future based on gut feelings about how well a >> completely different branch is doing. >> >> How can I reconcile these disparate points of view? How does one >> focus on testing and upgrade cycle for an "appropriately supported >> release" when the decision for the support cycle is completely up >> in the air? > On Sep 16, 2008, at 12:47 PM, Robert Watson wrote: > The FreeBSD Project, as with any other company or organization, > responds to events as they occur. We try to plan ahead, and when > things go better or worse than expected, we sometimes change the > plans. As far as I know we've never *shortened* the expected > support timeline for any branch or release, but we have on occasion > lenthened them when we feel it's important to do so. I'm not sure > what other answer is possible. No other answer. But nobody has yet provided what the EoL period is going to be. I have no problems with a period being extended ;-) But the business needs to know the minimum EoL for a given release to determine if upgrading to that release is viable. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?0C2C7E9B-61E3-4720-B76F-4745A3C963DA>