Update:Remora: Difference between revisions
Jump to navigation
Jump to search
(→Bugs: adding remora dev tracking bug) |
No edit summary |
||
| Line 13: | Line 13: | ||
* [[Update:Remora Localization|Remora Localization (l10n)]] | * [[Update:Remora Localization|Remora Localization (l10n)]] | ||
* [[Update:Remora Meeting Notepad|Remora Meeting Notepad]] | * [[Update:Remora Meeting Notepad|Remora Meeting Notepad]] | ||
* [[Update:Remora Permissions|Remora Permissions]] | |||
* [[Update:Remora Requirements|Remora Requirements]] | * [[Update:Remora Requirements|Remora Requirements]] | ||
* [[Update:Remora Schema|Remora Schema]] | * [[Update:Remora Schema|Remora Schema]] | ||
Revision as of 22:57, 2 November 2006
- Remora Database Migration
- Remora Developer/Admin Pages
- Remora Idea Dump
- Remora Interactions
- Remora Feeds (RSS)
- Remora Licensing
- Remora Localization (l10n)
- Remora Meeting Notepad
- Remora Permissions
- Remora Requirements
- Remora Schema
- Remora Schedule
- Remora Standards
- Remora Testing
- Remora Load Testing
- Remora Server Requirements
Bugs
Remora master tracking bug: bug remora Remora Developer Pages tracking bug: bug remora-dev
Remora Developer Pages tracking bug: bug remora-dev
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!