Issue #2157: F31 Self-Contained Change: Xfce 4.14 - fesco

fesco

#2157 F31 Self-Contained Change: Xfce 4.14

Closed: Accepted 4 years ago by churchyard. Opened 4 years ago by bcotton.

Xfce desktop environment has version 4.13.x which is currently available in Fedora. Significant work has been completed to migrate the DE to GTK-3 completely. The obvious benefit to this migration is the use of a modern and actively maintained toolkit.

Xfce 4.14 is a stable release with proven components, provide features users. This change proposal is submitted to sync fedora packages with the latest upstream releases.

churchyard commented 4 years ago

ignatenkobrain commented 4 years ago

+1 ofc :)

If you need somebody to review some new packages which are prereq for this change, feel free to assign those reviews to me.

zbyszek commented 4 years ago

bookwar commented 4 years ago

@bcotton the links to mail list discussions point to fesco elections instead of the xfce discussion

As I got from the mailing list XFCE 4.14 is not yet released and expected to have final release on 2019-08-11 See XFCE4 roadmap

And the Change Checkpoint: Completion deadline (testable) for Fedora 31 is 2019-08-13.

I think it is worth adding this info in the Change page, to show that release schedules were checked and that there is a plan how to achieve the goal not waiting for the last moment.

churchyard commented 4 years ago

Worth noting that we are already on 4.13 (4.14 pre-release) in Fedora 29 and 30.

So if we don't make it till the deadline, we'll not end up in some weird pre-release state - not any more than we are already in now.

So definitively even if it's not "final 4.14" on beta freeze checkpoint, it will be testable.

That said, a zero day update to "final" would be fine with me as well.

psabata commented 4 years ago

bcotton commented 4 years ago

@bcotton the links to mail list discussions point to fesco elections instead of the xfce discussion

Fixed, thanks!

Edited 4 years ago by bcotton

bcotton commented 4 years ago

From a schedule perspective, I'm not concerned. As @churchyard pointed out, it's already testable today. The more important deadline for this particular change is the Beta freeze, which starts Tue 2019-08-27.