Rodney M Dyer wrote:
> The developer builds and release
> candidates have not been installing and have been having errors when the
> AFS service started.

I feel compelled to point out the fact that I have seen zero bug reports
saying that OpenAFS would not install or that the service would not
start (except on Windows Vista and that is because of bugs in Vista.)

Now it turns out that as I test the software in my spare time I do come
across most of the problems, I cannot do it alone.  I don't have all of
the software configurations that end users are using at my disposal.  At
the moment I attempt to test on XP SP2, 2003 SP1, XP 64, and the latest
Vista builds.  I periodically get around to testing on 2000 workstation
and server.  The reality is though that the process of testing is very
time consuming.  It is for everyone.

What would be really helpful is if there were a group of people who
would volunteer to act as testers for each release.  If we had a
volunteer for each platform who would agree to test each release with
a few days and report back the results, that would be so beneficial to
the community.  It would also allow the Gatekeepers to focus on other
things.

On the Windows platform one of the bugs in the recent builds was a bug
that only affected a first time install.  Since 99% of my installations
are upgrades this bug slipped through the cracks.  I discovered it
before it was reported only due to a fluke.

If you are interested in volunteering, please send an e-mail with the
list of operating system releases on which you are willing to test.
We can design a checklist of things that should be tested for each
release.  Then a report can be made to the openafs-win32-devel list
after each release with the results.

Right now the Gatekeepers frequently are forced to make a blind call on
whether or not a release is really ready for prime time due to the lack
of positive feedback.  We don't know whether lack of bug reports means
we've done good or simply that no one is willing to take the first step.

What do you say?

Jeffrey Altman

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to