Task #141
closed
Determine Redmine releases, milestone, and upstream/downstream process
100%
Description
There are a few things we want to get out of using Redmine that are currently not in place. This story is somewhat of a catch all for those deliverables:
1. Knowing progress towards a given release. It should be easy to tell what stories and fixes are included in a given release, and how complete that overall effort is.
2. Same as (1) but for sprints. Same problem there.
3. The data in the version/releases field is currently global. It should not be because otherwise a given project (ie: docker plugin) won't easily have its own versioning scheme.
4. Determine a process to track the inclusion/QE/status, etc of a bug or story for a specific version. Ie: if a bugfix lands in multiple -dev branches and a -testing branch how can we track that?
5. Implement automation to automatically mark a corresponding bugzilla bug as POST when the upstream bug goes to MODIFIED.
Updated by bmbouter over 7 years ago
- Subject changed from Determine Redmine releases/mileston process to Determine Redmine releases/milestone process
Updated by bmbouter over 7 years ago
- Sprint/Milestone deleted (
12)
This never got started so I'm removing it from Feb sprint, and marking it as a Sprint Candidate
Updated by bmbouter over 7 years ago
- Subject changed from Determine Redmine releases/milestone process to Determine Redmine releases, milestone, and upstream/downstream process
- Description updated (diff)
- Priority changed from Normal to High
Updated by bmbouter over 7 years ago
- Tags Groomed added
- Tags deleted (
Sprint Candidate)
Added by regularuser over 7 years ago
Updated by bmbouter over 7 years ago
- Status changed from ASSIGNED to 6
- % Done changed from 90 to 100
Updated by bmbouter over 7 years ago
- Sprint Candidate set to Yes
- Tags deleted (
Sprint Candidate)
Updated by dkliban@redhat.com about 7 years ago
- Status changed from 6 to CLOSED - CURRENTRELEASE
.
141 - Validate and keep up-to-date redmine and bugzilla data
Adds a Jenkins job definition which periodically runs a python script. The Python script validates that upstream and downstream bugs have bi-directional relationships. The script also replicates upstream issue status to the downstream external tracker info. A report of issues identified and changes made are sent to a list of admins.
re #141