#7018 F27 stable push requests
Closed: Fixed 6 years ago Opened 6 years ago by adamwill.

This ticket will be used for requesting pushes of tested blocker / freeze exception fixes during F27 release freezes. See ​​​​​​https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and ​​​​​​https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process . Similar to candidate compose request tickets, this ticket can be closed by releng after each push and re-opened by QA each time a new push is needed.

Please push:

== Blockers ==


Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

There's one more we should push:

desktop-backgrounds-27.0.0-1.fc27 f27-backgrounds-27.0.0-2.fc27 for https://bugzilla.redhat.com/show_bug.cgi?id=1489164 - the update doesn't directly fix that bug, but the bug is a tracker and the update fixes one of its child bugs. Once it's pushed stable we can tell if we need to do anything more to get the backgrounds into GNOME, KDE and Xfce.

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Hi,
could you push this update:

Metadata Update from @pschindl:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @maxamillion:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @pschindl:
- Issue status updated to: Open (was: Closed)

6 years ago

In addition to the previous comment, please also push stable:

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

@kparal - can we add cloud-init-0.7.9-9.fc27 since it is +1 FE and has enough karma?

Please push these updates stable:

@dustymabe We're not including any FE at this moment unless we decide to slip a week.

Metadata Update from @pschindl:
- Issue status updated to: Open (was: Closed)

6 years ago

@dustymabe We're not including any FE at this moment unless we decide to slip a week.

Why not? It's standard to include FEs if they're ready and have enough karma, where is this policy/decision documented and why @kparal

It's standard to include them if they are well tested, well in advance, believed to be safe, and do not threaten our schedule to be slipped (which is this case, if we want to release this week, which might or might not work, we can't risk that the compose will fail in any way). Some details are here:
https://fedoraproject.org/wiki/QA:SOP_compose_request
https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

You may also request that pending fixes for freeze exception bugs are included in release candidate composes. Freeze exception bugs are those that do not block the release, but which have been accepted as being of sufficient importance that fixes may be allowed through the freeze: see the QA:SOP_freeze_exception_bug_process for further details. During release freezes, release engineering may push freeze exception fixes to the stable repository, but if a fix for a freeze exception issue is still pending stable status, and you judge the issue to be of sufficient importance and the fix to be sufficiently safe, you may list it for inclusion in the release candidate compose. Release engineering may question this decision if they consider it risky. Err on the side of caution when requesting inclusion of pending freeze exception fixes in release candidate composes.

But I and @pschindl are just apprentices here, @adamwill usually handles this. We might be doing it wrong, and Adam's on PTO right now. If you believe some FE should definitely be included today, let's have a discussion about it. If we slip, I of course intend to pull the safe FEs to stable.

So in the case of cloud-init we should add that as it fixes issues with cloud/atomic without impacting other components.

I'm going to be requesting FE fixes for aarch64 because ATM we don't have ANY aarch64 and that is a problem. Those will be for bugs 1491045 and 1489604 which are both accepted FEs.

@dustymabe releng has the right to refuse to include FE's if releng deems it too risky, we do not have to include FE's by their nature. the only thing we "have" to include is blocker fixes. given the extremely tight schedule and the fact we are looking to slip two weeks already, I am with QA and agree we should limit the risks.

we should pull in things that are blockers for alt arches

So for aarch64 I have accepted freeze exceptions:

RHBZ # 1491045 - grub2-2.02-18.fc27
RHBZ # 1489604 - shim-signed-13-0.6 shim-unsigned-aarch64-13-3.fc27 shim-unsigned-x64-13-3.fc27

So, some of these were not used in the RC2 compose, which is going to cause a lot of confusion, unless you also request a RC3. Is that planned?

We want the stable state to be what is the release (it gets tagged in koji after we are go) and having some things in stable, not in the compose will confuse people and not actually fix some things.

I see, thanks for spotting this. I'll let you know whether we request RC3 or not in a few hours, and update this ticket accordingly.

@kparal Asked on releng channel, but asking it here again:

[11:01:15] 19<28+19mboddu>? kparal: https://pagure.io/releng/issue/7018#comment-468096 some of those are already in the compose, we will push them to stable once we are a go, no need of a special request. And some of them are not in compose, is that mean that we should push them to stable or put them in the compose, either way we need a new compose request for them.

Initiated the push to stable on the above.

Metadata Update from @kellin:
- Issue assigned to kellin

6 years ago

Metadata Update from @kellin:
- Assignee reset

6 years ago

Metadata Update from @kellin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @pschindl:
- Issue status updated to: Open (was: Closed)

6 years ago

Initiated push to stable for the above two packages requested.

Metadata Update from @kellin:
- Issue status updated to: Closed (was: Open)

6 years ago

Please push the following updates stable:

  • anaconda-27.20.1-6.fc27 for #1495204

Metadata Update from @mohanboddu:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Some more requests for F27 Final / Server Beta fixes:

== Blockers ==

== Freeze exceptions ==

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @puiterwijk:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Few more to go:

== Blockers ==

== Freeze exceptions ==

Not requesting gnome-boxes yet as I'm not sure we actually want the virtio change any more.

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

sugar-browse-201.2-1.fc27 sugar-speak-54-3.fc27 sugar-read-119-1.fc27 sugar-write-98.3-1.fc27 for #1507296

We also need sugar-0.110.0-6.fc27 for #1490668

This set of stable pushes is done.

Metadata Update from @puiterwijk:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Done. :evergreen_tree:

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

Metadata Update from @adamwill:
- Issue status updated to: Open (was: Closed)

6 years ago

Metadata Update from @mohanboddu:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

6 years ago

I've checked and it looks like we're now done with stable pushes; all packages that were included in RC-1.6 have gone stable.

Login to comment on this ticket.

Metadata