> Would you mind explaining to TjL and the others why getting the
> features they most need is a bad thing if those features come too quickly!
>
It's the engineering and release process I'm thinking of. How many days
of automated testing do you put each release through? How much
controlled beta? You seem to have a staggering amount of release
churn. I've seen several companies in recent years make concerted
efforts to back off from release-of-the-week to a more planned and
managed process. (That has nothing at all to do with rapid iteration
within the development process itself, which is a good idea.)
> And, while you're at it, explain why Snapper, a "real" company, has
> lost almost all of its most vocal customers over the past year. Or
> are the only "real" companies those you have worked for?
>
First, you assume that vocal customers are something special to have, as
opposed to customers as a whole.
Second, I don't only consider the companies I've worked for (and with)
to be real -- but I do think that HP, Symantec (then VERITAS), VMware,
IBM, and many others know quite a bit about healthy release processes...
SPONSORED LINKS
| Palm os | Handspring treo | For palm os |
| Palm os database | Palm os software |
YAHOO! GROUPS LINKS
- Visit your group "treo" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
