On 25. sep. 2006, at 23.01, Mark Crispin wrote:
On Mon, 25 Sep 2006, Frode Nordahl 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 didn't have much success in the past with calling later
development snapshots "release candidates". On the one hand, there
are people who won't try even a release candidate because "it isn't
a release"; on the other hand, there are people who will complain
how disturbing it is that they encountered a bug in a release
candidate.
Name the it "test release", "technology preview" or "developer
preview" then.
I don't expect everybody to try every development snapshot. On the
other hand, mix support has been in the development snapshot for
months, and the timezone problem was in it since the beginning.
This means that *nobody* in the eastern hemisphere tested mix in
*any* development snapshot.
I know that I would test it if my attention was drawn to it earlier,
and you get my attention by throwing something out, and say "hey,
test this" :-)
I have been excited about this new format ever since I learned about
it, but due to time constraints, I have to defer my testing of any
new technology until I know that it is supposed to actually work. And
I need some sort of heads up to know when that happends.
--
Frode Nordahl
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
