Version field needs to be plugin independent like the Target Release field is
The version field in Redmine is shared across all projects. This makes the choice of version harder than it needs to be, and its likely doesn't have all necessary versions for all of the components that use it. Redmine uses custom fields to track this data so this task should build off of or modify that.
What is needed is the version field to become several version fields. The following ones are what we need. The release branches should be looked at to populate the data when this custom field is created.
Version(shared by platform, puppet, and rpm)
Version - Crane
Version - Debian
Version - Deployment
Version - Docker
Version - Nectar
Version - OpenStack
Version - OSTree
Version - Packaging
Version - Python
#3 Updated by bmbouter over 6 years ago
- Tracker changed from Issue to Task
- Status changed from ASSIGNED to CLOSED - CURRENTRELEASE
- Sprint/Milestone set to 16
- Groomed set to No
- Sprint Candidate set to No
This really is a task. It's not included in any actual code, nor is it documentation. I started on it because it was a bug. It's done now.
You'll notice the 'version' field values for nectar, Python support, Platform, etc are all different. I picked some sane defaults, but I can add/modify them further as needed.
Since this won't go to QE and is already in affect I'm moving this to CLOSED - CURRENTRELEASE
Please register to edit this issue