From Fedora Project Wiki
(Initial GNOME 3.32 Change)
 
m (Minor typos)
Line 36: Line 36:
The schedule for GNOME 3.32 releases doesn't align perfectly with Fedora 30 and we may need to request Freeze Exceptions during the release process. QA and GNOME packagers are familiar with the process and should be able to make a good call when it's appropriate to request an exception.
The schedule for GNOME 3.32 releases doesn't align perfectly with Fedora 30 and we may need to request Freeze Exceptions during the release process. QA and GNOME packagers are familiar with the process and should be able to make a good call when it's appropriate to request an exception.


Right now it seems likely that we need an exception to get GNOME 3.31.92 into F30 Beta a few days after the freeze has started, to make sure we get the maximum amount of testing for the new code that is going to be shipped in F30. Final 3.30.0 is just a week after that (with just cricital bug fixes and translation updates compared to 3.31.92 rc) and may require another freeze exception.
Right now it seems likely that we need an exception to get GNOME 3.31.92 into F30 Beta a few days after the freeze has started, to make sure we get the maximum amount of testing for the new code that is going to be shipped in F30. Final 3.32.0 is just a week after that (with just cricital bug fixes and translation updates compared to 3.31.92 rc) and may require another freeze exception.


=== Fedora 30 Schedule ===
=== Fedora 30 Schedule ===
Line 96: Line 96:
Install Workstation, make sure that the desktop and all apps are usable. Participate in GNOME 3.32 test day (TBD).
Install Workstation, make sure that the desktop and all apps are usable. Participate in GNOME 3.32 test day (TBD).


We are continuously keeping GNOME in Rawhide (and Branched once it's branched from Rawhide) up to date as upstream releases 3.31.x development snapshots, leading up to the final 3.30 release. Everybody can participate in the testing by installing Fedora development releases on personal desktop computers and reporting regressions.
We are continuously keeping GNOME in Rawhide (and Branched once it's branched from Rawhide) up to date as upstream releases 3.31.x development snapshots, leading up to the final 3.32 release. Everybody can participate in the testing by installing Fedora development releases on personal desktop computers and reporting regressions.


For issues that are not Fedora-specific, the best place to report issues and reach developers is usually at https://gitlab.gnome.org/GNOME
For issues that are not Fedora-specific, the best place to report issues and reach developers is usually at https://gitlab.gnome.org/GNOME

Revision as of 13:56, 5 January 2019

GNOME 3.32

Summary

Update GNOME to the latest upstream release, 3.32.

Owner

  • Name: Kalev Lember
  • Email: klember@redhat.com
  • Release notes owner:
  • Product: Workstation
  • Responsible WG: Workstation

Current status

  • Targeted release: Fedora 30
  • Last updated: 2019-01-05
  • Tracker bug: <will be assigned by the Wrangler>

Detailed Description

The new features for 3.32 include: TBD

The schedule for GNOME 3.32 releases doesn't align perfectly with Fedora 30 and we may need to request Freeze Exceptions during the release process. QA and GNOME packagers are familiar with the process and should be able to make a good call when it's appropriate to request an exception.

Right now it seems likely that we need an exception to get GNOME 3.31.92 into F30 Beta a few days after the freeze has started, to make sure we get the maximum amount of testing for the new code that is going to be shipped in F30. Final 3.32.0 is just a week after that (with just cricital bug fixes and translation updates compared to 3.31.92 rc) and may require another freeze exception.

Fedora 30 Schedule

2019-03-05 Fedora 30 Beta Freeze
2019-03-26 Fedora 30 Beta Release (Preferred Target)
2019-04-02 Fedora 30 Beta Release (Target #1)
2019-04-16 Fedora 30 Final Freeze
2019-04-30 Fedora 30 Final Release (GA) (Preferred Target)
2019-05-07 Fedora 30 Final Release (GA) (Target #1)

GNOME 3.32 Schedule

2019-03-06 GNOME 3.31.92 rc release
2019-03-13 GNOME 3.32.0 release
2019-04-10 GNOME 3.32.1 release

Benefit to Fedora

Fedora stays in sync with upstream and gets the latest features and bug fixes.

Scope

  • Proposal owners:
    • Keep existing GNOME packages updated
    • Package new applications and new dependencies of existing GNOME packages for GNOME 3.32
    • Work with QA to fix any release blocking regressions
    • Work with upstream to fix any release blocking regressions
  • Other developers: N/A
  • Release engineering: Create f30-gnome side tag after F30 is branched from rawhide
  • Policies and guidelines: N/A (not a System Wide Change)
  • Trademark approval: N/A (not needed for this Change)

Upgrade/compatibility impact

Upgrading from GNOME 3.30 to 3.32 should be seamless for users.

How To Test

Install Workstation, make sure that the desktop and all apps are usable. Participate in GNOME 3.32 test day (TBD).

We are continuously keeping GNOME in Rawhide (and Branched once it's branched from Rawhide) up to date as upstream releases 3.31.x development snapshots, leading up to the final 3.32 release. Everybody can participate in the testing by installing Fedora development releases on personal desktop computers and reporting regressions.

For issues that are not Fedora-specific, the best place to report issues and reach developers is usually at https://gitlab.gnome.org/GNOME

User Experience

Notable additions or changes to the GNOME user experience in 3.32 include:

  • TBD

Dependencies

N/A

Contingency Plan

GNOME 3.32 will be released in March 2019 and fits well into Fedora 30 schedule. In case of issues with individual modules that aren't either released in time or aren't deemed suitable for Fedora 30, we'll continue using the GNOME 3.30 versions of these modules.

  • Contingency mechanism: The Workstation WG evaluates the GNOME 3.32 prerelease first before beta freeze and reverts individual changes as needed, and then does another evaluation before the final freeze.
  • Contingency deadline: beta freeze
  • Blocks release? Yes
  • Blocks product? Workstation

Documentation

Release Notes