MCBastos wrote:
Interviewed by CNN on 06/10/2011 20:12, Paul B. Gallagher told the
world:
1) rapid release tends to promote sloppy work, products not ready
for prime time, and poor product reduces market share;
Actually, KaiRo argued very convincingly that the rapid release has
exactly the opposite effect:
<http://home.kairo.at/blog/2011-08/why_rapid_releases_can_improve_stability>
Finally got around to reading this. Although there are spots where
half-German syntax makes it unreadable ("we have switches of some way we
can throw") -- Entschuldigung! -- I got enough of the overall gist to
understand his points.
Robert may well be right that the rapid-release scheme has produced good
results, by some objective measure. But that's surprising, and it's not
what people here are saying, by and large.
The usual expectation, based on experience in a wide variety of fields,
is that "haste makes waste," so if we see someone rushing and making
mistakes, we usually attribute the mistakes to the rushing. So the
question here is whether the devs are working too fast in order to meet
unreasonable deadlines (and this question should be asked regularly), or
whether they're working at a normal, reasonable pace but releasing their
work more often, in smaller increments (and expanding the tester base).
In the latter case, the second concern I identified still applies --
"rapid release forces users to adapt quickly and often, and most users
don't like that unless it's for new features important to them."
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
