For some projects, set FixReleased on merged changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| OpenStack Core Infrastructure |
Fix Released
|
Low
|
Monty Taylor |
Bug Description
I'd like the update_bug script to directly set merged changes to FixReleased for openstack-manuals. I've talked it over with Thierry our release manager and he thinks it's the correct setting for the way our docs are published immediately to trunk (or a release named for stable/diablo for example) when a merge occurs.
Same for devstack (requested by anotherjesse)
Same for openstack-
Changed in openstack-ci: | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
tags: | added: updatebug |
summary: |
- For openstack-manuals, set FixReleased on merged changes + For some projects, set FixReleased on merged changes |
description: | updated |
Changed in openstack-ci: | |
milestone: | none → folsom |
description: | updated |
Changed in openstack-ci: | |
importance: | Wishlist → Low |
status: | Confirmed → Triaged |
assignee: | nobody → Thierry Carrez (ttx) |
Changed in openstack-ci: | |
assignee: | Thierry Carrez (ttx) → Monty Taylor (mordred) |
status: | Triaged → In Progress |
Reviewed: https:/
Committed: http://
Submitter: Jenkins
Branch: master
commit 38693e0a39210fd
Author: Monty Taylor <email address hidden>
Date: Sat May 19 10:04:01 2012 -0400
Skip fix committed for some projects.
There are a set of projects which release directly from git,
so we can just set them directly to fix released.
Fixes bug 943413.
Change-Id: I0186b67efaa5ee
Changed in openstack-ci: | |
status: | In Progress → Fix Committed |
Changed in openstack-ci: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/7597
Review: https:/