EdgyIdeas

Differences between revisions 53 and 54
Revision 53 as of 2006-06-14 01:24:12
Size: 6845
Editor: studiocity-motorola-bsr1-70-36-194-85
Comment: linkification, mark trivial items
Revision 54 as of 2006-06-14 01:24:35
Size: 6860
Editor: studiocity-motorola-bsr1-70-36-194-85
Comment:
Deletions are marked like this. Additions are marked like this.
Line 127: Line 127:
 * Formal process for gathering feature ideas from the community (currently random mixture of mailing lists, wiki pages, blueprint, etc.)  * Formal process for gathering feature ideas from the community (currently random mixture of mailing lists, wiki pages, blueprint, wishlist bugs, etc.)

These are my personal notes about possible projects for EdgyEft and beyond. It is not a place for suggestions from others. For that, see CommunityEdgyIdeas.

Infrastructure

Features

Release Process

  • Deadline for spec approvals
  • Dapper release post-mortem

Testing

https://launchpad.net/distros/ubuntu/+spec/edgy-testing

  • Explicit milestone regression testing (early and often)
    • Test plans
    • Laptop testing team
    • CD testing team
  • Incorporate multilingual testing
  • Coalesce non-overlapping test cases (e.g., partitioner vs. OEM)
  • Monitor testing progress regularly (SimonLaw)

  • Adapt test case assignments for bandwidth as well as hardware (SimonLaw)

  • Client-side application for guided and semi-automated testing

Community

  • Forums
    • Involve more in formal testing efforts
    • QA of FAQ answers, etc.
  • Formal process for gathering feature ideas from the community (currently random mixture of mailing lists, wiki pages, blueprint, wishlist bugs, etc.)

MattZimmerman/EdgyIdeas (last edited 2008-08-06 16:32:07 by localhost)