Project

Profile

Help

Task #141

Determine Redmine releases, milestone, and upstream/downstream process

Added by bmbouter over 5 years ago. Updated over 1 year ago.

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

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Pulp 2
Sprint:
March 2015

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.

Associated revisions

Revision 1fb0232f View on GitHub
Added by regularuser over 5 years ago

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

History

#1 Updated by mhrivnak over 5 years ago

  • Description updated (diff)

#2 Updated by bmbouter over 5 years ago

  • Subject changed from Determine Redmine releases/mileston process to Determine Redmine releases/milestone process

#3 Updated by mhrivnak over 5 years ago

  • Priority changed from Normal to High

#4 Updated by rbarlow over 5 years ago

  • Tags Sprint Candidate added

#5 Updated by mhrivnak over 5 years ago

  • Sprint/Milestone set to 12

#6 Updated by bmbouter over 5 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

#7 Updated by mhrivnak over 5 years ago

  • Priority changed from High to Normal

#8 Updated by bmbouter over 5 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

#9 Updated by bmbouter over 5 years ago

  • Tags Groomed added
  • Tags deleted (Sprint Candidate)

#10 Updated by bmbouter over 5 years ago

  • Tags Sprint Candidate added

#11 Updated by bmbouter over 5 years ago

  • Assignee set to bmbouter

#12 Updated by bmbouter over 5 years ago

  • Sprint/Milestone set to 13

#13 Updated by bmbouter over 5 years ago

  • Sprint/Milestone changed from 13 to 14

#14 Updated by bmbouter over 5 years ago

  • Status changed from NEW to ASSIGNED

#15 Updated by bmbouter over 5 years ago

  • % Done changed from 0 to 90

#16 Updated by bmbouter over 5 years ago

  • Status changed from ASSIGNED to 6
  • % Done changed from 90 to 100

#17 Updated by bmbouter over 5 years ago

  • Groomed set to Yes
  • Tags deleted (Groomed)

#18 Updated by bmbouter over 5 years ago

  • Sprint Candidate set to Yes
  • Tags deleted (Sprint Candidate)

#19 Updated by dkliban@redhat.com almost 5 years ago

  • Status changed from 6 to CLOSED - CURRENTRELEASE

#21 Updated by bmbouter over 2 years ago

  • Sprint set to March 2015

#22 Updated by bmbouter over 2 years ago

  • Sprint/Milestone deleted (14)

#23 Updated by bmbouter over 1 year ago

  • Tags Pulp 2 added

Please register to edit this issue

Also available in: Atom PDF