Update:Remora: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 18: | Line 18: | ||
* [[Update:Remora Load Testing|Remora Load Testing]] | * [[Update:Remora Load Testing|Remora Load Testing]] | ||
* [[Update:Remora Server Requirements|Remora Server Requirements]] | * [[Update:Remora Server Requirements|Remora Server Requirements]] | ||
== Bugs == | == Bugs == | ||
Revision as of 22:30, 20 October 2006
- Remora Database Migration
- Remora Developer/Admin Pages
- Remora Idea Dump
- Remora Interactions
- Remora Licensing
- Remora Meeting Notepad
- Remora Requirements
- Remora Schema
- Remora Schedule
- Remora Standards
- Remora Testing
- Remora Load Testing
- Remora Server Requirements
Bugs
Remora master tracking bug: bug remora
Remora bugs should have TM 3.0.
Bug severity meanings, suggested:
- Blocker: bug prevents work on one or more launch requirements for Remora
- Critical: bug represents dataloss or security issue
- Major: bug corresponds to a launch requirement for Remora
- Normal: desirable for Remora launch, but not a strict requirement
- Minor or lower: will take if it's there and doesn't break anything else, or eat too much design/review/etc. bandwidth
Should we grow some blocking flags? Doesn't feel like we need them yet!