Re: Should we have a release manager for each release? (or, "who owns rawhide"?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Feb 15, 2018, at 5:39 PM, Adam Williamson wrote:

> In practice it tends to boil down to "me, nirik, and puiterwijk".

Meanwhile, there are probably hundreds of people on this -devel
list who are capable of debugging and fixing things - some very
experienced engineers, yet some of them are here busily debating
minor things about spec files.

It doesn't make any sense at all to have hundreds (thousands?)
of people whose sole power is to increment the versions of
packages they own, and a tiny subset of people who are capable
of e.g. reverting changes.

First step: Close down the #fedora-releng channel and discuss
problems in #fedora-devel.  Releasing is not a distinct problem
from development, and people should have experience in *both*
roles.

Two next steps:

 - Empower anyone to submit a pull request that can *revert* changes
   (e.g. the push steved just did to libevent) - not necessarily to
   merge it, but merging the PR should actually revert (e.g. it should
   also fix koji's state)
 - Generate a process to pick e.g. at least one person from each
   edition WG, plus perhaps more from various subsystems like Anaconda to be
   "on point" each day/week - and empower them to merge those PRs.

Another step:

 - Create a process to "close the tree", like Mozilla does for Firefox.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux