Re: Upcoming Releases Schedule...

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


_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Upcoming Releases Schedule...
    ... 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. ... 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. ... Security Officer for a minimum of 12 months after the release. ... I don't know of any COTS software house that really does it any differently, and I'm not sure you could do it differently -- no one plans to ship a lemon, but once in a while you discover that things don't go as planned. ...
    (freebsd-stable)
  • Re: challenge: end of life for 6.2 is premature with buggy 6.3
    ... and then observe the EoL get pushed. ... I'm sorry that the FreeBSD project failed to conform to your ... release picked by the team to be support for,.. ... the attitude and opinion you have right now accomplishes nothing other than alienating your supporters. ...
    (freebsd-stable)
  • Re: challenge: end of life for 6.2 is premature with buggy 6.3
    ... and then observe the EoL get pushed. ... I'm sorry that the FreeBSD project failed to conform to your ... release picked by the team to be support for,.. ... The OP stated there are unclosed bugs that be believes are preventing him from using 6.3 and called into question the decision of EoL'ing 6.2. ...
    (freebsd-stable)
  • RE: S/W End of Life
    ... Subject: S/W End of Life ... Once support has been dropped, you can still try to find existing fixes, ... What I do when I am forced to support a product past EOL is to make sure ...
    (bit.listserv.ibm-main)
  • Re: challenge: end of life for 6.2 is premature with buggy 6.3
    ... and then observe the EoL get pushed. ... I'm sorry that the FreeBSD project failed to conform to your ... release picked by the team to be support for,.. ... The option provided seems like a fairly good compromise to both interests. ...
    (freebsd-stable)