Bug 1571046 - Need final build for F28 (fedora-release-notes)
Summary: Need final build for F28 (fedora-release-notes)
Alias: None
Product: Fedora
Classification: Fedora
Component: fedora-release-notes
Version: rawhide
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: John J. McDonough
QA Contact: Fedora Extras Quality Assurance
Whiteboard: AcceptedBlocker
Depends On:
Blocks: F28FinalBlocker
TreeView+ depends on / blocked
Reported: 2018-04-24 02:20 UTC by Adam Williamson
Modified: 2018-04-25 00:03 UTC (History)
16 users (show)

Fixed In Version: fedora-release-notes-28.01-2.fc28
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-04-25 00:03:54 UTC
Type: Bug

Attachments (Terms of Use)

Description Adam Williamson 2018-04-24 02:20:49 UTC
We have a Final criterion: "Any release notes included in the release repositories and/or any release-blocking deliverables must be for the correct release, and approved for release by the documentation team."

As things stand, fedora-release-notes is still in the 'standard' comps group for F28, which means it's certainly in multiple release-blocking media. That means we need release notes that are "for the correct release" and "approved for release by the documentation team".

The current package build for F28 is fedora-release-notes-27.01-1.fc28 , which is certainly not "for the correct release" and I'm going to assume is not "approved for release by the documentation team". Thus, proposing this as a Final blocker.

Docs folks, we really need some shippable release notes sent out as a Koji build plus Bodhi update by, at the latest, tomorrow North American time - thanks!

Comment 1 Brian Exelbierd 2018-04-24 12:50:20 UTC
If I have done this correctly, a build is running at https://koji.fedoraproject.org/koji/taskinfo?taskID=26537685

Comment 2 Brian Exelbierd 2018-04-24 12:52:10 UTC
So I did something wrong with the build, however it should have built correctly.  Is this a permission issue?

Comment 3 Stephen Gallagher 2018-04-24 13:02:44 UTC
Adam, it appears that *you* retired and blocked this package back in F27:

It was never unretired (and at this point would require a new package review). Do we want to do this, or shall we move to just ensuring that a public Release Notes page exists on the web? (This would also be easier to keep updated if information needs adjustment).

Comment 4 Matthew Miller 2018-04-24 14:43:18 UTC
Here's the last go-round: bug #1506052. We _talked_ about retiring it, but then Brian and Igor put out a package at the last minute.

Comment 5 Matthew Miller 2018-04-24 14:44:56 UTC
So, I think: if this got retired, it was retired in error, and I think that should be able to be un-done without a package re-review.

Comment 6 Adam Williamson 2018-04-24 14:47:47 UTC
Yeah, we're doing that. It seems I retired it on master as well as f27. Not sure why I would've done that, but it doesn't seem to be what we intended or discussed.

Comment 7 Matthew Miller 2018-04-24 14:52:56 UTC
(In reply to Adam Williamson from comment #6)
> Yeah, we're doing that. It seems I retired it on master as well as f27. Not
> sure why I would've done that, but it doesn't seem to be what we intended or
> discussed.

It *was* what we intended at one brief point in the saga, but then we stopped intending that and did something else and never went back and corrected it. Release got out the door, and it's not terribly surprising that we never thought of it again. :)

Comment 8 Fedora Update System 2018-04-24 15:07:33 UTC
fedora-release-notes-28.01-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-0999b53c30

Comment 9 Mohan Boddu 2018-04-24 17:11:54 UTC
Since we have a build now

+1 Blocker

Comment 10 Stephen Gallagher 2018-04-24 17:15:53 UTC
+1 blocker

Comment 11 Adam Williamson 2018-04-24 17:46:00 UTC

Comment 12 Fedora Update System 2018-04-25 00:03:54 UTC
fedora-release-notes-28.01-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.