On 10/7/2011 3:05 PM, Paul B. Gallagher wrote:
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."
Just to address these parts here...
1) We are working at the same pace we usually did. The rapid release
process gives us some better leeway here for:
* We notice things we need to fix in our code a bit earlier.
* We actually release all our fixes/changes faster.
It is not any different in our overall timing, (I don't see anyone
rushing, really.)
2) The releases are *all* addressing security concerns, and in the old
system the frequency of security releases was more often ~ every 4
weeks, which is less often than our major releases now. So if you ignore
the frustration of addon breakages (a valid concern) is the same
experience upgrade frequency wise as now.
--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
