Date: Wed, 24 Nov 1999 07:06:36 -0800 From: Cy Schubert - ITSD Open Systems Group <Cy.Schubert@uumail.gov.bc.ca> To: stable@FreeBSD.ORG Subject: Re: speaking of 3.4... Message-ID: <199911241506.HAA75693@cwsys.cwsent.com> In-Reply-To: Your message of "Tue, 23 Nov 1999 10:41:00 PST." <Pine.BSF.4.10.9911231028460.60522-100000@best.llama.com>
next in thread | previous in thread | raw e-mail | index | archive | help
How many times have I seen this discussion on this list?! I've been
using FreeBSD on various types of hardware since 2.0.5. The only stability
problems I've had were around the time of 2.1 and 2.1.1. IMO every FreeBSD
release has been more stable.
If you feel there are stability issues either roll up your sleeves and
help out or go back to RedHat (which IMO is much less stable)!
Regarding the release schedule, does it really matter whether i'ts a
release every three months or ever four months. If it's that much of
an issue, skip every other release. IME, sometimes we have 3 releases
a year, other times 4.
If you're a CDROM customer, it's only $24. $24 is not much to pay for
good software! If you can't afford $24, you need to focus on the real
problems in your life -- forget FreeBSD and work out your personal problems
out first!
For those of you who refuse to test before -release. You get what you
deserve!
Regards, Phone: (250)387-8437
Cy Schubert Fax: (250)387-5766
Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca
ITSD Cy.Schubert@gems8.gov.bc.ca
Province of BC
"e**(i*pi)+1=0"
In message <Pine.BSF.4.10.9911231028460.60522-100000@best.llama.com>, Sam Habas
h writes:
> > When we're already at 4 releases/year, this is indicitive of a
> > problem. People want new releases to fix the bugs in the current release.
>
> People want new releases to add functionality. Bugfixes happen constantly,
> that's the whole point to tracking -STABLE and being on this mailing list.
>
> > Our release QA is horrible. Look at what Apple does -- they sit on the
> > release candidate for a *month*, with *no changes at all*, before putting
> > it gold; we might get a week, and frequently there's last-minute changes
> > or more obscure nuances that often result in bugs in the release.
>
> Maybe Apple can loan the FreeBSD project some QA engineers then. I hear
> they work for daemon decals in lieu of the many tens of thousands of
> dollars a year they otherwise tend to ask for, qualified or unqualified,
> EACH. But you raise a good point: are there people tasked with doing
> QA work, or are we relying on users to submit PRs? I've always assumed
> the latter procedure was what was occuring, if not by design, then by
> necessity.
>
> FreeBSD has a different paradigm for releasing its software than commercial
> concerns, with attendant strengths and weaknesses. I don't really have
> the knowledge to disagree with your point, but the flip side of your
> aregument is that going a *month* with *no changes at all* may be
> unacceptable to the goal of maintaining a -STABLE (if not stable) release.
>
> --Sam
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-stable" in the body of the message
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199911241506.HAA75693>