Re: challenge: end of life for 6.2 is premature with buggy 6.3



On Jun 6, 2008, at 11:41 PM, Adrian Chadd wrote:
As said before, the reason FreeBSD isn't supporting older 6.x releases
anymore is because there's just no manpower to do so.

Which is what I was asking about. I've asked the questions more specifically since they apparently weren't phrased well the first time. It would be great to hear answers to those questions.

I still don't think you get it. FreeBSD is a community. A community
works when enough people contribute positively towards furthering the
goals of the project. Jo is a user. He sounds like he is using it in
some reasonably critical and money-earning roles. Jo can participate
by testing stuff on test hardware, reporting back issues and working
with the community.

Which I do. If you check out my bug reports they almost always include patches.

I've also added freebsd support to many projects, including full package management in the latest versions of cfengine.

Bitching about there being no long-term support
for releases isn't constructive. Some developer comments may not be
constructive either, but this is a -community project-. Join the
-community- and help out.

Am I missing an ID card? Where should I go to acquire one?

When there is a specific issue I can help with, I do. In this case I was asking about the justification for dropping support so quickly.

It doesn't matter if running a long-term support project would be
beneficial for a certain subset of the userbase, its a losing
situation to cater to them unless they somehow contribute back to the
community.


I work on bugs for things I can help with. I add freebsd support to various projects. I test and report bugs on new releases. I spend at least 10% (and sometimes more) of my paid $EMPLOYER's time working on freebsd things, and countless hours of unpaid time. I don't know that I can do any more than this.

--
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: 2.6.19 -mm merge plans
    ... I actually expected people to dislike arbitrary rules more than they do, but I've come to believe that people _like_ having rules that they have to obey, as long as it's not a big pain for them. ... So I think that a "odd release"/"even release" rule that clarifies what a certain mid-point in the release cycle actually _means_, even if it doesn't necessarily add anything else, might be a good thing. ... Then after people stop reporting show stoppers, change to rc numbers, where rc versions are actually candidates for release without known major bugs. ...
    (Linux-Kernel)
  • Re: Inheritance
    ... Go hooking to fix bugs in MS code? ... There's no site for reporting bugs in VS ... >> always be using the latest DDK. ... Maxim Shatskih, Windows DDK MVP ...
    (microsoft.public.development.device.drivers)
  • Re: First day with production development on D2005
    ... >> involved in reporting them vs. the benefit of reporting them. ... > The cost is taking some time to write the report. ... bugs are unlikely to get fixed and that show-stopper, ... not bother reporting bugs and if the development environment has too many ...
    (borland.public.delphi.non-technical)
  • Re: Wolfram Alpha claims to be a primary source.
    ... D> But your manner of reporting bugs, ... D> newsgroups in a dramatic way is not the best approach. ... It's probably not an unreasonable assumption that had Vladimir been professional about the way he reported bugs, he may well have been considered for employment by Maplesoft, Wolfram Research, perhaps Mathworks too. ...
    (sci.math.symbolic)
  • Re: Delphi 2007 more Flakey than 2006?
    ... I don't know how difficult this would be - as my bugs are all my own ... Windows has such a reporting system on board - called WER (Windows ... which attaches the stack trace similar to what Windows error ...
    (borland.public.delphi.non-technical)