Ticket #4985 (closed task: fixed)

Opened 5 years ago

Last modified 15 months ago

Extend test image creation SOP to require notification of delays

Reported by: adamwill Owned by: rel-eng@…
Milestone: Component: other
Keywords: Cc: robatino
Blocked By: Blocking:


Working through the F16 QA retrospective here:


One of the notes is:

"jlaska - Alpha TC1 - Missed the Alpha-TC1 milestone by 1 week, little to no communication regarding status. With only two weeks Alpha ISO test time, losing 50% of time almost certainly results in a slip. See rel-eng ticket#4844 . None of the Alpha rel-eng release tickets have been filed at this time.

adamw - perhaps releng image compose SOP should require updating of ticket with progress info, especially when image compose / delivery is delayed?"

So: this ticket proposes that the releng 'Composing test images' SOP - https://fedoraproject.org/wiki/Composing_test_images - should be extended to require whoever is creating the images to post a comment on the image request ticket if the compose is delayed, explaining the reasons for the delay (so that any other interested party can attempt to contribute to resolving them) and giving a best estimate of an ETA if possible (so other groups can adjust their scheduling as best they can).


Change History

comment:1 Changed 5 years ago by adamwill

Now I look at it closely, that SOP is for RATS image compose, not for full candidate build compose. There appears to be no SOP for full candidate build compose. One should probably be created.

comment:2 Changed 5 years ago by robatino

  • Cc robatino added

comment:3 Changed 3 years ago by till

  • Component changed from koji to other

I changed the component, because this does not appear to be a koji-related ticket.

comment:4 Changed 15 months ago by kevin

  • Status changed from new to closed
  • Resolution set to fixed

I don't think there's anything controversial here.

Typically if there are delays they are discussed on irc, but I think updating the ticket would be great too.

I updated the wiki page about this.

Note: See TracTickets for help on using tickets.