From Fedora Project Wiki
Ongoing prioritization for release tools work from Matt Miller via bi-weekly sync.
Fedora priorities: https://fedoraproject.org/wiki/ReleaseEngineering/PriorityPipeline
17NOV15
- What kind of priority does this actually carry? It was listed as urgent 19 months ago :/
03NOV15
- Will need to discuss what we want to do for signing long term (after we get our immediate high priority items resolved)
- Need to talk to Kushal about creating an assignee at the test level for bugyou so that depending on the test that fails we get it to the right team for resolution
- would also need to know where each report should be filed (which may include having teams set up a BZ queue)
- Consider posting about priorities on the Fedora Blog?
- Collecting feedback from stakeholders on changes
- reaching out to direct individuals first, followed by the mail to dev list when submitted for review should be sufficent
- Moving demos to once a month
20OCT15
- Any high priority BZs or Trac issues we need to be aware of?
- We should get to this eventually as a team
- Replace a grooming meeting once a month with a BZ/Trac issue grooming
- Updates to priority list - https://fedoraproject.org/wiki/ReleaseEngineering/PriorityPipeline
- Updates on developing priorities
- RHEL.next
- Potential future priority: everything needed to build RHEL is its own toolset and shipped on its own lifecycle
- Sigul support
06OCT15
- Cloud images produced in a format that is basically qcow3 but it's still called qcow2
- This breaks openstack
- imcleod is working on a patch for koji
- needs to get applied ASAP
- this has to be done for images that will be part of the F23 release
- Potential future priority: everything needed to build RHEL is its own toolset and shipped on its own lifecycle
- Public notes
- Suggest that we use either wiki or google doc (but people aren't going to like that)
- Sigul support
- Need to make a case and an explicit request to Denise if we need resources
- Will make the sigul task assessing and formulating this