I got feedback from Adam and Ben today; so the following changes have
I have added a little paragraph at the beginning to say what a last
minute blocker bug is. I used freeze as the time anchor rather than a
meeting since that seems to be the most firm time constraint we work to.
Perhaps the review meetings could be anchored to the freeze as well.
There might be some merit to showing the critical meetings in the
schedule list that gets published.
I changed "team" to "stakeholder groups"
I removed "proposed" from places where it really didn't add anything.
Have a Great Day!
I look forward to speaking/writing and learning from you all.
In terms of location, I’m in NYC’s borough of Queens and am hoping to make it up to devconf 2019 if anyone else might be up there too!
Danny Lee <dreamer(a)panix.com>
I have been impressed with the urgency of doing. Knowing is not enough;
we must apply. Being willing is not enough; we must do. ~ Leonardo da Vinci
I've created a python3 Fedora 29 update 3 weeks ago:
I don't want to push it without a single user giving feedback, however it is a
security update, so I don't want to keep it in testing forever.
Anyone still running F29 who could update to this python3 version and run the
system for couple days?
Please forgive all my dumb questions.
I need just a clarification. What are release blocking architectures nowadays?
In the test matrix there is ARM alongside x86_64.
This means armv7hl or aarch64?