Confirmed users, Bureaucrats and Sysops emeriti
1,531
edits
User talk:ChrisHofmann/QuarterlyReleases: Difference between revisions
Jump to navigation
Jump to search
User talk:ChrisHofmann/QuarterlyReleases (view source)
Revision as of 19:44, 7 January 2011
, 7 January 2011→Using History as a Guide
ChrisHofmann (talk | contribs) |
ChrisHofmann (talk | contribs) |
||
| Line 91: | Line 91: | ||
The history also shows a slowly increasing cycle over time as it was harder and harder to maintain the rapid pace. We can also find ways to measure and possibly combat this effect as we try to get back on a faster pace. | The history also shows a slowly increasing cycle over time as it was harder and harder to maintain the rapid pace. We can also find ways to measure and possibly combat this effect as we try to get back on a faster pace. | ||
Getting back on a faster pace also will have challenges. It took awhile to ramp to the fast pace of 2001, and we learned over time that for every 1 month of serious development work on the trunk at least 1 to 1.5 months have been required in beta to shake out problems. This rule seems to apply to both short development cycles and long ones like with | Getting back on a faster pace also will have challenges. It took awhile to ramp to the fast pace of 2001, and we learned over time that for every 1 month of serious development work on the trunk at least 1 to 1.5 months have been required in beta to shake out problems. This rule seems to apply to both short development cycles and long ones like with Firefox 3.0, and in the cases as we continue to roll in features over a consecutive betas. Once the development cycle starts to increase it gets harder and harder to get the cat back in the bag. Shipping off trunk frequently helps to stay out of the vicious circle of longer development periods requiring longer betas. | ||
== Impact On Quality == | == Impact On Quality == | ||