When it comes to Testing Ubuntu GNOME, we need to make sure everything is working as expected without any problem.
That said, we would like to invite you to help Ubuntu GNOME with Upgrade Testing.
How to help Ubuntu GNOME with Upgrade Testing?
The idea is very simple. We need to upgrade Ubuntu GNOME 13.10 to Ubuntu GNOME Trusty Tahr and test the upgrade process.
If you have Ubuntu GNOME 13.10 installed already, we would really appreciate your help in this regard.
If Ubuntu GNOME 13.10 is not installed, then kindly install it and do the upgrade. Installing Ubuntu GNOME from LiveUSB should not take more than 10 minutes.
How to do an upgrade from 13.10 to Trusty Tahr?
Before we get into this, kindly have a read at Upgrades Documentation.
Whether you’re helping Ubuntu GNOME Team with Testing or you’re a fan of running unstable releases on your machine, kindly make sure to backup your important files before anything else.
To upgrade Ubuntu GNOME 13.10 Stable to Ubuntu GNOME Trusty Tahr Development Release, kindly have a read at Upgrading to Development Releases.
Share your Testing Results
Please make sure to share your Testing Results with Ubuntu GNOME QA Team. The more feedback in this regard, the better.
Let’s make sure that our very first LTS Release of Ubuntu GNOME is solid as rock.
Thank you for helping, supporting and testing Ubuntu GNOME!
As always, for more information about testing, please see Ubuntu GNOME Testing Wiki Page.
Should you have any question, please don’t hesitate to Contact Us.
If you are using OpenSSL (or ever did use it with any of your current keypairs in the last 3-4 years), you are probably in a rush to upgrade all your systems and replace all your private keys right now.
If your certificate authority is CACert.org then there is an extra surprise in store for you. CACert.org has changed their hash to SHA-512 recently and some client/server connections silently fail to authenticate with this hash. Any replacement certificates you obtain from CACert.org today are likely to be signed using the new hash. Amongst other things, if you use CACert.org as the CA for a distributed LDAP authentication system, you will find users unable to log in until you upgrade all SSL client code or change all clients to trust an alternative root.
A few last pieces are being worked in the last couple of days to final
- James Page is struggling to find a release team member to review the docker.io feature freeze exception request (bug 1295093).
- The juju-quickstart MIR is deferred; Robie will upload some final bugfixes soon.
- Louis is working on some last minute fixes to sosreport.
- Parameswaran reports that all smoke tests are passing.
- Stefan is polishing some last pieces in Xen and libvirt.
Full minutes: https://wiki.ubuntu.com/MeetingLogs/Server/20140408
T/master-next: LP1303657 (“Cannot boot trusty kernel on qemu-system-arm”) – we
were missing the correct dtb (wasn’t necessary in S) and qemu was waiting for a
console over jtag (HVC_DCC) that would never show up – waiting for a
confirmation from the reporter before sending the patches.
Release Metrics and Incoming Bugs
Release metrics and incoming bug data can be reviewed at the following link:
Milestone Targeted Work Items
4 work items
2 work items
1 work item
2 work items
3 work items
Status: Trusty Development Kernel
We entered into Kernel Freeze for Trusty last Thurs and have uploaded
what we intend to be the final kernel for Trusty, 3.13.0-23.45. All
patches from here on out are subject to our Ubuntu SRU policy and only
critical bug fixes will warrant an upload before release next week.
Important upcoming dates:
Thurs Apr 17 – Ubuntu 14.04 Final Release (~1 week away)
The current CVE status can be reviewed at the following link:
Status: Stable, Security, and Bugfix Kernel Updates – Saucy/Raring/Quantal/Precise/Lucid
Status for the main kernels, until today (Mar. 25):
- Lucid – Verification and Testing
- Precise – Verification and Testing
- Quantal – Verification and Testing
Saucy – Verification and Testing
Current opened tracking bugs details:
For SRUs, SRU report is a good source of information:
cycle: 30-Mar through 26-Apr
28-Mar Last day for kernel commits for this cycle
30-Mar – 05-Apr Kernel prep week.
06-Apr – 12-Apr Bug verification & Regression testing.
17-Apr 14.04 Released
13-Apr – 26-Apr Regression testing & Release to -updates.
Open Discussion or Questions? Raise your hand to be recognized
No open discussion.