On Mon, 25 Sep 2006, Aaron W. LaFramboise wrote:
I think it would really help to announce and release a beta or release
candidate some time before the release, as this most certainly will make
more people test and hopefully find more of these problems before the final
release hits the press.
I'd like to second this motion. Calling for extensive testing of a "release
candidate" is common practice in some other Internet-based software projects,
and perhaps this strategy would be successful here as well.
As my previous message indicated, I've been there, done that, and got the
T-shirt. Calling something a "release candidate" has been of dubious
benefit in the past, and has created its own problems.
The difference with the other Internet-based software projects is that
many of these projects have a team of developers in different locations
working on it. That's not the case here.
Although I'm a member of the Pine team, I'm the only one who works on
c-client/imapd. The feedback I get from my teammates primarily occurs
when I break something that they use, or they need some new service from
c-client. My teammates are all using mix, but in the same environment
that I use.
Thus, I am pretty much all there is for first-order testing. That's why I
put those development snapshots out there.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
