fesco

Clone
Source Code
GIT

#1967 Fedora 29 incomplete changes
Closed: Accepted 5 years ago Opened 5 years ago by bcotton.

Closed: Accepted
Reopen Issue

On Tuesday, August 14th, 2018 we have reached the Change Checkpoint: Completion deadline (testable). At this milestone all the F29 Changes should be in "Testable" state, which is indicated by "MODIFIED" status of a tracking bug. The following link points to Bugzilla to show all the tracking bugs which are not in "MODIFIED" state and are not considered as "Testable".

Not-testable changes

These changes are presented for FESCo review to determine what action should be taken.

The following is a static list of incomplete changes:

2018-08-16 — Edited to remove UEFI for ARMv7 and Basic FPGA support. Change Owner reports they are in testable state.
Edited 5 years ago by bcotton

Metadata Update from @maxamillion:
- Issue tagged with: meeting
5 years ago

Stop building 389-ds-base on i686 → actually done, I set the state to ON_QA

Make dbus-broker the default DBus implementation → mostly done, waiting for fedora-release to be updated

mpfr-4.0.0 → this one does not look good, since there's no visible activity. A new package for the new version was considered, but this doesn't seem to have happened.

This was discussed in yesterday's FESCo meeting:

AGREED: Defer mpfr to Fedora 30 (+1: 5, -1: 0, +0: 0) (maxamillion, 16:08:26)
ACTION: zbyszek to talk to change owner about sponsorship (zbyszek, 16:19:17)

AGREED: defer "update festival to 2.5" until next week, zbyszek to take point on following up (+1: 6, +0: 0, -1: 0) (maxamillion, 16:20:00)

https://fedoraproject.org/wiki/Changes/Label_Our_Variants#Contingency_Plan (bowlofeggs, 16:24:01)
AGREED: Label Out Variants will be go with Contingency Plan 1 if not completed by beta freeze (+1: 5, -1: 0, +0: 1) (maxamillion, 16:33:02)

AGREED: allow a week to get an update on the state of Merge Dstat And Performance Co-Pilot (+1: 5, -1: 0, +0: 0) (maxamillion, 16:37:32)

Stop building 389-ds-base on i686 is actually complete and no longer requires discussion as an incomplete Change (maxamillion, 16:38:47)

https://pagure.io/pungi-fedora/pull-request/631 (dustymabe, 16:43:14)
AGREED: wait one more week for a status update on Silverblue rename (+1: 6, -1: 0, +0: 0) (maxamillion, 16:48:04)

Updates from today's FESCo meeting.

  * AGREED: "update festival to 2.5": Defer to F30 unless implemented by
    F29 devel freeze (+6, 0, -0)  (contyk, 16:49:18)

  * AGREED: cloud image updates: defer and check next week, it's unclear
    to me what would need to be done before beta as this change deals
    with post GA content (+7, 0, -0)  (contyk, 16:51:37)

  * AGREED: "Rename Atomic Workstation to Silverblue": let folks work on
    it today, if not done in time for freeze, they can ask for an
    exception or move to f30. (+7, 0, -0)  (contyk, 16:32:34)

Changes not code-complete by the beginning of the Beta freeze

Dynamic link

Static list:

Update festival to 2.5
Status: Not ready: needs packager sponsorship (see comment #4)

The sponsorship is done, and the package was reviewed. I caused a snafu by asking the name to be updated after the package was reviewed and accepted (speech_tools → speech-tools). This caused a slight delay, but both the package that needed sponsorship and the update to festival are happening. Since the festival package right now is completely broken, delaying this Change to F30 is IMHO not in the interest of users. The amount of duplicates raised against the original bug about festival not working is large enough to suggest that people are impacted by this. Festival is a leaf package that can be updated without much impact on the rest of the distribution. Thus, I think we should just allow the packages to be updated (either provide a freeze exception or wait until after the beta freeze is over).

One additional not-ready change:
Edited 5 years ago by bcotton

Update festival to 2.5
Status: Not ready: needs packager sponsorship (see comment #4)

The sponsorship is done, and the package was reviewed. I caused a snafu by asking the name to be updated after the package was reviewed and accepted (speech_tools → speech-tools). This caused a slight delay, but both the package that needed sponsorship and the update to festival are happening. Since the festival package right now is completely broken, delaying this Change to F30 is IMHO not in the interest of users. The amount of duplicates raised against the original bug about festival not working is large enough to suggest that people are impacted by this. Festival is a leaf package that can be updated without much impact on the rest of the distribution. Thus, I think we should just allow the packages to be updated (either provide a freeze exception or wait until after the beta freeze is over).

It doesn't end up on any install media that I know about, so it doesn't really need a freeze-exception (it'll be in the updates-testing repo, which is enabled for anyone who installs the Beta), so I'm +1 to letting it land whenever the packager can make it happen.

One additional not-ready change:

Make dbus-broker the default DBus implementation
Tracking bug: #1557954
Status: Waiting for merges (see comment #11)
Owner: @dvdhrm @tomegun

Hmm, if the switch hasn't already happened, I'm not particularly comfortable with letting them land this as blocker/FE changes now that we're in Beta Freeze. And, of course, if it doesn't make it out in the Beta, it won't get sufficient testing to trust it for GA. So I guess I'm (unhappily) going to have to recommend that this be bumped to F30. D-BUS is fundamental to a huge amount of the plumbing of Fedora and I don't want to see it rushed in post-Freeze.

dbus-broker

The discussion of dbus-broker was moved to #1986, let's ignore it here.

Update festival to 2.5

no recent changes, I asked in the bug for an update.

Cloud provider image updates:

From https://bugzilla.redhat.com/show_bug.cgi?id=1619451#c5:

This change is an internal process change that has no code changes inside of Fedora 29. This change should not block the release of Fedora 29.

It seems we don't need to worry about it now.

Rename Atomic Workstation to Silverblue

Not sure about the status of this one. Even if it is not complete, backing it out now would probably be more work than keeping/finishing what we have.

We will discuss this during Monday's meeting at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.

New ticket has been created to discuss "Silverblue renaming" as https://pagure.io/fesco/issue/1989.

Updates from today's meeting:

dbus-broker

We agreed to track this in #1986.

Update festival to 2.5

AGREED: we will wait for festival to be done and push in the new version after beta if it is ready before GA (+8, 0, -0)

Cloud provider image updates

FESCo acks the cloud image updates change and notes that they need to be ready after GA

Rename Atomic Workstation to Silverblue

we will file a separate fesco ticket about the silverblue change, ask for status there, and vote there (+8, 1, -0)

@zbyszek has filed that ticket at #1989.

With the separate Silverblue ticket, I think this should be closed, yes? Am I missing anything else here?

Festival is still not finished. We can either close this, or leave it open as a reminder.

@zbyszek OK, I'l mark this as stalled then and take it off the meeting agenda.

Metadata Update from @sgallagh:
- Issue untagged with: meeting
- Issue tagged with: stalled
5 years ago

Sadly the Festival upgrade missed F29. Nothing we can do at this point, let's close.

Metadata Update from @zbyszek:
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)
5 years ago

Metadata Update from @zbyszek:
- Issue untagged with: stalled
5 years ago

Login to comment on this ticket.

Metadata
None
None
None
None
None
Powered by Pagure 5.13.3
Documentation • File an Issue • About • SSH Hostkey/Fingerprint
© Red Hat, Inc. and others.