From owner-freebsd-qa Mon Dec 20 17:50:21 1999 Delivered-To: freebsd-qa@freebsd.org Received: from staff.accessus.net (staff.accessus.net [209.145.151.3]) by hub.freebsd.org (Postfix) with ESMTP id 7D950153FE; Mon, 20 Dec 1999 17:50:14 -0800 (PST) (envelope-from doogie@staff.accessus.net) Received: by staff.accessus.net with Internet Mail Service (5.5.2650.21) id ; Mon, 20 Dec 1999 19:50:13 -0600 Message-ID: From: Jason Young To: 'Colin' , freebsd-qa@FreeBSD.ORG Cc: "'jkh@freebsd.org'" Subject: RE: After 3.4 finally goes out the door Date: Mon, 20 Dec 1999 19:50:12 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF4B55.B8B7227A" Sender: owner-freebsd-qa@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF4B55.B8B7227A Content-Type: text/plain; charset="iso-8859-1" I think it's a good idea to keep the list around, but I don't think that the QA volunteers were really used to their full potential. I tested when I could (early in the testing cycle), and I feel that most of my efforts were for naught, because as usual, a large percentage of the commits in the testing period were very last minute (after most or all of the QA builds). Yeah, it's a free software project and nobody's paid, and what gets out the door is still a fine piece of work (and major kudos to jkh and the rest of the guys on that). But, I don't think much meaningful testing of the real release was accomplished due to all the really really late changes. The last minute "oh I really need such and such MFC'd" trips are killers (sysinstall, moused, you won't have to rack your brain too hard for examples). I assume that the schedule for 3.5-RELEASE is pretty much set already. Would it be possible to back most of that schedule up about a week, and in the week before the CD is cut, put the "pretty-much-final, we-really-mean-it, won't touch it unless the release is definitely fscked" up for general FTP? If the schedules are set well in advance, nobody will be hurting or complaining of the loss of one week's time in a three or four month -STABLE release cycle. The QA volunteers need a set release to assure its quality, ya know? This is no extra work or major change for anyone. I think that if we could get the "frozen" release candidate out there in front of people for at least a week or so, we could muchly reduce the size of our ERRATA files. > -----Original Message----- > From: Colin [mailto:cwass99@home.com] > Sent: Monday, December 20, 1999 7:18 PM > To: freebsd-qa@FreeBSD.ORG > Subject: After 3.4 finally goes out the door > > > I realize we got off to a rather slow start, but all > things considered > better than many expected. My question is, is there any > intent for this list > to survive the release of 3.4, as basically a home for people with the > time/energy/hardware to talk about testing? > I think it would be a marvelous idea, assuming > sufficient interest of > course, to continue this with 4.0-RC when that starts the > long arduous path > from -CURRENT ;) > > Cheers, > Colin > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-qa" in the body of the message > ------_=_NextPart_001_01BF4B55.B8B7227A Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: After 3.4 finally goes out the door

I think it's a good idea to keep the list around, but = I don't think that the QA volunteers were really used to their full = potential.

I tested when I could (early in the testing cycle), = and I feel that most of my efforts were for naught, because as usual, a = large percentage of the commits in the testing period were very last = minute (after most or all of the QA builds).

Yeah, it's a free software project and nobody's paid, = and what gets out the door is still a fine piece of work (and major = kudos to jkh and the rest of the guys on that). But, I don't think much = meaningful testing of the real release was accomplished due to all the = really really late changes. The last minute "oh I really need such = and such MFC'd" trips are killers (sysinstall, moused, you won't = have to rack your brain too hard for examples).

I assume that the schedule for 3.5-RELEASE is pretty = much set already. Would it be possible to back most of that schedule up = about a week, and in the week before the CD is cut, put the = "pretty-much-final, we-really-mean-it, won't touch it unless the = release is definitely fscked" up for general FTP? If the schedules = are set well in advance, nobody will be hurting or complaining of the = loss of one week's time in a three or four month -STABLE release cycle. = The QA volunteers need a set release to assure its quality, ya know? = This is no extra work or major change for anyone.

I think that if we could get the "frozen" = release candidate out there in front of people for at least a week or = so, we could muchly reduce the size of our ERRATA files.

> -----Original Message-----
> From: Colin [mailto:cwass99@home.com]
> Sent: Monday, December 20, 1999 7:18 PM
> To: freebsd-qa@FreeBSD.ORG
> Subject: After 3.4 finally goes out the = door
>
>
>      I realize we got = off to a rather slow start, but all
> things considered
> better than many expected.  My question = is, is there any
> intent for this list
> to survive the release of 3.4, as basically a = home for people with the
> time/energy/hardware to talk about = testing?
>      I think it would = be a marvelous idea, assuming
> sufficient interest of
> course, to continue this with 4.0-RC when that = starts the
> long arduous path
> from -CURRENT ;)
>
> Cheers,
> Colin
>
>
> To Unsubscribe: send mail to = majordomo@FreeBSD.org
> with "unsubscribe freebsd-qa" in the = body of the message
>

------_=_NextPart_001_01BF4B55.B8B7227A-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-qa" in the body of the message