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 85: | Line 85: | ||
One would be to understand the weak points of the development model, and watch for the return of the same side effects. | One would be to understand the weak points of the development model, and watch for the return of the same side effects. | ||
More build and test automation, and better version control systems than we had in 2001-2004 will probably help to combat the effects developers taking on smaller projects to match quarterly releases. But, the web is still hard. Some significant projects may require new strategies for getting the kind of field | More build and test automation, and better version control systems than we had in 2001-2004 will probably help to combat the effects developers taking on smaller projects to match quarterly releases. But, the web is still hard. Some significant projects may require new strategies for getting the kind of field testing and longer beta cycles needed to ship major features in core gecko. | ||
The code complexity issues associated with lots of extra build and run-time flags to be able to turn off features and/or development them "under the hood" also deserves so thought. Figuring out plans for cleaning these up after their useful lifetime ends and other strategies also need consideration. | The code complexity issues associated with lots of extra build and run-time flags to be able to turn off features and/or development them "under the hood" also deserves so thought. Figuring out plans for cleaning these up after their useful lifetime ends and other strategies also need consideration. | ||