Confirmed users
2,615
edits
Calendar:Development Strategies: Difference between revisions
Jump to navigation
Jump to search
→Basic Bug/Feature Workflow
| Line 14: | Line 14: | ||
; 1. Get UI buyoff : Doing this before worrying about the implementation avoids large rewrites because of basic design differences. | ; 1. Get UI buyoff : Doing this before worrying about the implementation avoids large rewrites because of basic design differences. | ||
; 2. Get basic code-level strategy agreement : Same benefit as 1. Even if you have a pretty good idea of how to attack a bug, the code owner may have big-picture information that would suggest a different strategy. | ; 2. Get basic code-level strategy agreement : Same benefit as 1. Even if you have a pretty good idea of how to attack a bug, the code owner may have big-picture (or little-picture) information that would suggest a different strategy. | ||
; 3. Code with <u>ongoing</u> discussion : When you're wondering about some implementation issue, or see red flags (like having to copy-and-paste chunks of code, adding weird dependencies, or violating abstractions), plunging ahead anyway is often the wrong thing to do. Instead, talk to a code owner or peer. Perhaps even post a patch fragment in the bug for input. | ; 3. Code with <u>ongoing</u> discussion : When you're wondering about some implementation issue, or see red flags (like having to copy-and-paste chunks of code, adding weird dependencies, or violating abstractions), plunging ahead anyway is often the wrong thing to do. Instead, talk to a code owner or peer. Perhaps even post a patch fragment in the bug for input. | ||
; 4. Review | ; 4. Review | ||