Chandler Alpha4 Debrief

"Best release ever!"

More of

screenshots in specs
discussions on visual design
designers
reframing/focus discussion to get to conclusion sooner (eg: sidebar icons)
small design meetings (eg: recurring events discussions)
high-level presentation of features (eg: sheila's presentation prepped for Mitch)
meeting notes that clarify decisions, open issues, next actions
design/UI review of feature before end of release (eg, addressing fields)
incremental updates
Plan on time for debug/stability work ("end-game mentality")
distinction between feature/code freeze
streamline bug triage process (let coder/reviewer make decision)
dogfooding
testing scenarios (added to test plan)
QA resources
timely summaries
recurrence tests (unit/functional)
Cosmo/Chandler coordination (0.5 qualification)
worrying about performance
less feature work, more performance work: attention to balance of features/performance/coherence.
allocating time in schedule for perf work
cutting features not critical path (good example: cutting printing)
better instructions for dogfooders (what to do when filing a bug, repo/bug submissions, etc)
external volunteers to help get more testing done - yay Davor! (Send t-shirts?)
more linux coverage / linux dogfooders
easier to debug & create functional tests
investment in functional tests framework
irc bug bashes
more fixing rare/random failures
verify more resolved bugs
long-running func tests
more Aparna back

bug council meeting every day
confusion around process rules
hard to diagnose functional test failures
waiting for tbox to be green
ignoring perf regressions
design proposals in bugzilla (move to design list) (If you're replying inline in bugzilla, it should be on list)
test frameworks

Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.