Calendar:Development Strategies: Difference between revisions

Calendar:Development Strategies (view source)

1 byte removed , 18 May 2006

Confirmed users

2,615

edits

@@ Line 11: / Line 11: @@
 == Basic Bug/Feature Workflow ==
-Lots of conflict can be avoided by careful ordering of work, and by ensuring that code and UI owners are all on the same page throughout the development process.  Over the years, the workflow that we've seen that's most effective for driving bugs and features into the tree with the least amount of pain looks something like this:
+Lots of conflict can be avoided by careful ordering of work and by ensuring that code and UI owners are all on the same page throughout the development process.  Over the years, the workflow that we've seen that's most effective for driving bugs and features into the tree with the least amount of pain looks something like this:
 ; 1. Get UI buyoff : Doing this before worrying about the implementation avoids large rewrites because of basic design differences.