Webdev:Meetings:2008-08-21: Difference between revisions
Jump to navigation
Jump to search
(New page: * Dev cycle changes (carry over from AMO discussion) ** Why are we feeling rushed or behind at code freeze? ** How should we change the cycle? ** morgamic's idea: 10 days dev time, 3 days ...) |
No edit summary |
||
| Line 3: | Line 3: | ||
** How should we change the cycle? | ** How should we change the cycle? | ||
** morgamic's idea: 10 days dev time, 3 days QA time, push, 2 days planning/down time during/after push, repeat | ** morgamic's idea: 10 days dev time, 3 days QA time, push, 2 days planning/down time during/after push, repeat | ||
** Ideas | |||
*** Push on a Tuesday instead - so code freeze thursday and push Tuesday instead | |||
*** Bugs in there can be very vague, so we should spend more time making things more specific or planning larger bugs into smaller pieces | |||
* Testing | * Testing | ||
** Need to start writing tests | ** Need to start writing tests | ||
Revision as of 20:09, 21 August 2008
- Dev cycle changes (carry over from AMO discussion)
- Why are we feeling rushed or behind at code freeze?
- How should we change the cycle?
- morgamic's idea: 10 days dev time, 3 days QA time, push, 2 days planning/down time during/after push, repeat
- Ideas
- Push on a Tuesday instead - so code freeze thursday and push Tuesday instead
- Bugs in there can be very vague, so we should spend more time making things more specific or planning larger bugs into smaller pieces
- Testing
- Need to start writing tests
- Not going to make eveyrone go back and write tests retro-actively
- However, we should focus more on writing simple tests (installation tests, syntax error checks, acceptance tests) for most of what we do
- Thoughts on how to "enforce" test writing?
- Jacob!
- Test cluster update
- SSO update and discussion