Update:Remora: Difference between revisions
Jump to navigation
Jump to search
(Added dashboard link) |
No edit summary |
||
| Line 4: | Line 4: | ||
* [[Update:Schedule|Remora Schedule]] | * [[Update:Schedule|Remora Schedule]] | ||
* [[Update:Remora Meeting Notepad|Remora Meeting Notepad]] | |||
* [[Update:Remora Requirements|Remora Requirements]] | * [[Update:Remora Requirements|Remora Requirements]] | ||
* [[Update:Remora Interactions|Remora Interactions]] | * [[Update:Remora Interactions|Remora Interactions]] | ||
Revision as of 17:33, 7 September 2006
- Remora Schedule
- Remora Meeting Notepad
- Remora Requirements
- Remora Interactions
- Remora Developer/Admin Pages
- Remora Dashboard w/ progress
- Remora Idea Dump
- Remora Schema
- Remora Database Migration
- Remora Standards
- Remora Testing
- Remora Server Requirements
- Radiant Core Preview
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!