But am I the only tester out there who doesn't think they'll keep
up with such a quick release schedule, and may skip one of the above?

No matter how many or few dev releases you put out, people are going
to miss all, some, or most of them - for a variety of reasons: mostly
because of time and convenience Time, because unless you're me :)
You have more important work-related things to do Convenience,
because it is sort of annoying to have to download and then reinstall
the program manually

It would be much easier to have an upgrade system that is a bit
more automatic - a command issued to the shell and, "bang!" your Dada
is updated The more convenience you have, the less time it takes and
the amount of people that will test out the beta's will increase

But, dev releases are important, since they do create a snapshot that
we can look back from I take the betas and test them on most of the
accounts I have access to

So, yeah, it's common for people to skip dev releases, even if
they're in the development For us, it's because there's no
incredibly easy way to have available the newest version to test If
people are just curious about the dev releases, and download/install
one out of the blue, they can still provide some valuable feedback
with their fresh pair of eyes

I understand the need for the next release to come ASAP, but I'm
curious why you project a need for another one following that (but before the
stable release)?

The way release candidates are supposed to work is that you release
one, and if there aren't any problems, you just rename it to become
the, "stable" release If there are problems, you fix them, and
release another release candidate, until you get it right ;)

2 9 had a very large dev cycle - it was a much larger release with
many core changes to the program 2 10 is mostly building upon those
core changes - we're playing with all the wiggle-room created

Justin Simoni