Project

Profile

Help

Task #836

closed

Version field needs to be plugin independent like the Target Release field is

Added by bmbouter over 7 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Pulp 2
Sprint:
May 2015
Quarter:

Description

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

Also available in: Atom PDF