Difference between revisions of "BexarDBMigrations"
m (Text replace - "__NOTOC__" to "") |
m (Text replace - "NovaSpec" to "NovaSpec") |
||
| Line 1: | Line 1: | ||
| − | * '''Launchpad Entry''': | + | * '''Launchpad Entry''': NovaSpec:db-versioning-and-migration |
* '''Created''': 2010-11-22 | * '''Created''': 2010-11-22 | ||
* '''Contributors''': [[DaveWalker]] | * '''Contributors''': [[DaveWalker]] | ||
Latest revision as of 23:31, 17 February 2013
- Launchpad Entry: NovaSpec:db-versioning-and-migration
- Created: 2010-11-22
- Contributors: DaveWalker
Contents
Summary
Release Note
Support for database schema migrations, rolling forwards and backwards. Testing schema version is correct when nova is launched.
Rationale
User stories
Assumptions
Design
You can have subsections that better describe specific parts of the issue.
Implementation
This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:
UI Changes
Should cover changes required to the UI, or specific UI that is required to implement this
Code Changes
Code changes should include an overview of what needs to change, and in some cases even the specific details.
Migration
None
Test/Demo Plan
This need not be added or completed until the specification is nearing beta.
Unresolved issues
This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.
BoF agenda and discussion
Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.
