Calendar:Development Strategies: Difference between revisions

Calendar:Development Strategies (view source)

64 bytes added , 18 May 2006

Confirmed users

2,615

edits

Revision as of 04:36, 18 May 2006 (view source) Dmose (talk \| contribs) (→‎Key success strategies) ← Older edit		Revision as of 04:38, 18 May 2006 (view source) Dmose (talk \| contribs) (→‎Key success strategies) Newer edit →
Line 31:		Line 31:
	** 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 critical, because difficulty to review often scales extremely non-linearly with patch size. 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 critical for reviewing, because difficulty to review often scales extremely non-linearly with patch size, but it also helps the developer 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.