Feature #373
Autogenerate config.xml and provide means to migrate it to newer versions
| Status: | Closed | Start date: | 05/11/2010 | |
|---|---|---|---|---|
| Priority: | (P3) Normal | Due date: | ||
| Assignee: | Sergey Bostandzhyan | % Done: | 0% |
|
| Category: | dSS | |||
| Target version: | 0.9.0-alpha1 | |||
| Severity: | Normal | |||
| Story points | - | |||
| Velocity based estimate | - |
Description
When no config.xml is available, the dSS should automatically generate a default one.
It each new version of the dSS should also provide means to upgrade older config.xml files to the latest version.
History
Updated by Miguel Rodriguez over 1 year ago
- Status changed from New to Assigned
- Assignee set to Patrick Stählin
- Target version set to 0.9.0-alpha1
Updated by Patrick Stählin over 1 year ago
- Status changed from Assigned to Feedback
Did we agree to close/reject this one? We do have a version attribute in the config and we haven't made any format breaking changes that I know of.
Updated by Patrick Stählin over 1 year ago
- Assignee changed from Patrick Stählin to Sergey Bostandzhyan
Updated by Sergey Bostandzhyan over 1 year ago
Since we now have the feature of config.d and subscription.d directories, "migration" when updating an installation is no longer necessary: all custom addons are now anyway separated from the main configuration files.
Updated by Sergey Bostandzhyan over 1 year ago
- Status changed from Feedback to Closed