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

Re: Buyer Beware: A Major Change in NFS is about to happen

Matej Cepl wrote:
> Case in question ... I am not allowed to fix bug https://
> bugzilla.redhat.com/show_bug.cgi?id=520998, which I have filed some time
> ago, watched that maintainer didn't do anything to it, finally after
> discussing it with OpenSSL maintainer I have decided that upgrading to
> the current stable version of the package makes a lot of sense, fixed the
> spec so that it builds, build it ... and found that I cannot push it to
> the bodhi, because I would need to humbly petition FESCO for permission
> to fix a bug.

In this case, as Josh Boyer pointed out, it already made F12 and even F12 
Beta, as you built it before the Final Devel Freeze.

But if you do build something during the freeze and want it to make F12, 
FESCo is not the responsible body, rel-eng is. Just file a tag request at:
and explain:
* what changes you did,
* what the benefit of those changes is (e.g. "fixes an important bug" (and 
please give URLs)),
* what testing you did on the new version to ensure it works,
* why you don't expect it to break things (e.g. "it's an upstream bugfix 
release, fully backwards-compatible, no major changes").
(You can look at some of the existing tag requests for freeze overrides to 
get an idea of how things should look like, and also of what kind of 
questions rel-eng asks if you don't fill in some of the above. ;-) )

Then you just need 2 rel-eng members to approve the tag request, which 
usually happens very quickly if you did your "homework" (see above).

        Kevin Kofler

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