Hi,
Thank you to all those who attended the F27 release retrospective! [1] We had some excellent discussions on what went well and what could have gone better during this past release cycle and compiled a document with all that feedback. [2] If you were unable to participate in the retrospective meeting, fear not! You still have the chance to contribute now...
*So what's next?*
Fedora Release Engineering is committed to continuous improvement, and we're looking to identify one area we should focus on improving during the F28 release cycle.
*Please vote on the feedback you feel would be most valuable to address in F28 by Friday, December 8 at 5PM UTC in the retrospective document. [2]*
*How do I vote?*
Place your vote for an item in the retrospective document [2] at the beginning of the bulleted feedback point by adding +1.
For example, if you believe improvements around the new packager tooling is the most valuable area to improve during F28, your vote will look the following:
- +1 The new packager tooling is not feature complete with the old tooling, and where it is feature complete it is more "cumbersome" to use.
Do NOT vote for action items. Please only vote for feedback. I noted some potential action items during the retrospective, however, we will only pursue addressing the top voted feedback. Whether or not that item already has an action item listed is irrelevant.
*How do I determine what to vote for?*
I recommend asking yourself the following questions when deciding what to vote on:
- What's "costing" release engineering the most if it's not fixed? Think of cost in terms of resources and time. - What's most "painful" for us? Think of a pain as what prevents release engineering from achieving timely, quality releases.
If you have any questions, don't hesitate to reach out.
[1] https://youtu.be/iPOuPIJzczU [2] https://public.etherpad-mozilla.org/p/FedoraRelease27RelEngRetrospective
KAITLYN CARCIA
aSSOCIATE PROJECT MANAGER, RCM
Red Hat Westford https://www.redhat.com/
T: +1-857-770-0448- M: +1-978-604-8667 IM: katec https://red.ht/sig
Hey all,
The votes are in and the winner (winner being what Fedora release engineering will focus on improving in F28) is...
#975 https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tooling/us/975?kanban-status=151 [1]: More project management oversight - helping people focus and re-evaluating current state more often would be useful
Thanks for all your contributions. This ticket is an official F28 action item. Please follow the ticket for details on implementation.
[1] https://taiga.fedorainfracloud.org/project/acarter-fedora-docker-atomic-tool...
KAITLYN CARCIA
aSSOCIATE PROJECT MANAGER, RCM
Red Hat Westford https://www.redhat.com/
T: +1-857-770-0448- M: +1-978-604-8667 IM: katec https://red.ht/sig
On Tue, Dec 5, 2017 at 2:41 PM, Kate Carcia kcarcia@redhat.com wrote:
Hi,
Thank you to all those who attended the F27 release retrospective! [1] We had some excellent discussions on what went well and what could have gone better during this past release cycle and compiled a document with all that feedback. [2] If you were unable to participate in the retrospective meeting, fear not! You still have the chance to contribute now...
*So what's next?*
Fedora Release Engineering is committed to continuous improvement, and we're looking to identify one area we should focus on improving during the F28 release cycle.
*Please vote on the feedback you feel would be most valuable to address in F28 by Friday, December 8 at 5PM UTC in the retrospective document. [2]*
*How do I vote?*
Place your vote for an item in the retrospective document [2] at the beginning of the bulleted feedback point by adding +1.
For example, if you believe improvements around the new packager tooling is the most valuable area to improve during F28, your vote will look the following:
- +1 The new packager tooling is not feature complete with the old
tooling, and where it is feature complete it is more "cumbersome" to use.
Do NOT vote for action items. Please only vote for feedback. I noted some potential action items during the retrospective, however, we will only pursue addressing the top voted feedback. Whether or not that item already has an action item listed is irrelevant.
*How do I determine what to vote for?*
I recommend asking yourself the following questions when deciding what to vote on:
- What's "costing" release engineering the most if it's not fixed?
Think of cost in terms of resources and time.
- What's most "painful" for us? Think of a pain as what prevents
release engineering from achieving timely, quality releases.
If you have any questions, don't hesitate to reach out.
[1] https://youtu.be/iPOuPIJzczU [2] https://public.etherpad-mozilla.org/p/FedoraRelease27RelEngRetrospec tive
KAITLYN CARCIA
aSSOCIATE PROJECT MANAGER, RCM
Red Hat Westford https://www.redhat.com/
T: +1-857-770-0448- M: +1-978-604-8667 IM: katec https://red.ht/sig
rel-eng@lists.fedoraproject.org