Calendar:Development Strategies: Difference between revisions

Calendar:Development Strategies (view source)

8 bytes removed , 18 May 2006

Confirmed users

2,615

edits

Revision as of 05:01, 18 May 2006 (view source) Dmose (talk \| contribs) (→‎Basic Bug/Feature Workflow) ← Older edit		Revision as of 05:03, 18 May 2006 (view source) Dmose (talk \| contribs) (→‎Key success strategies) Newer edit →
Line 33:		Line 33:
	** see also point 5 of [http://www.mozilla.org/hacking/development-strategies.html the Development Strategies document].		** see also point 5 of [http://www.mozilla.org/hacking/development-strategies.html the Development Strategies document].

	*; split work into manageable pieces : This is especially critical for reviewing, because difficulty to review often scales extremely non-linearly with patch size, ~~but~~ it also rewards ~~the developer~~ by allowing ~~him or her~~ to land ~~code~~ sooner. Points 7, 8, and 12 of the [http://www.mozilla.org/hacking/new-features.html Developing New Mozilla Features page] address this in great detail.		*; split work into manageable pieces : This is especially critical for reviewing, because difficulty to review often scales extremely non-linearly with patch size. However, it also rewards developers by allowing code to land sooner. Points 7, 8, and 12 of the [http://www.mozilla.org/hacking/new-features.html Developing New Mozilla Features page] address this in great detail.