#593 kernel 5.2 test week
Closed: Fixed 4 years ago by sumantrom. Opened 5 years ago by jforbes.

Owner: Justin Forbes
Time Frame: July 22nd-26th
Features: Kernel 5.2 rebase

As discussed at Flock, we will start hosting test days for each major kernel rebase (approximately every 8-10 weeks). Last time it was discussed that we should extend this to a test week, to allow time for more participants. They have been incredibly helpful so far. As the 5.2 kernel is now released, I would like to get a test week in before we push the rebase to stable releases. I will have ISOs for USB images so that users can test on bare metal or in VMs, and the kernel will be available in the stabilization repo for users who wish to install it on existing systems.


Hey Justin,
Thanks for filing the issue, I will go ahead and set up the bits!

On Mon, Jul 8, 2019, 19:03 Justin M. Forbes pagure@pagure.io wrote:

jforbes reported a new issue against the project: fedora-qa that you are
following:
``
Owner: Justin Forbes
Time Frame: July 22nd-26th
Features: Kernel 5.2 rebase

As discussed at Flock, we will start hosting test days for each major
kernel rebase (approximately every 8-10 weeks). Last time it was discussed
that we should extend this to a test week, to allow time for more
participants. They have been incredibly helpful so far. As the 5.2 kernel
is now released, I would like to get a test week in before we push the
rebase to stable releases. I will have ISOs for USB images so that users
can test on bare metal or in VMs, and the kernel will be available in the
stabilization repo for users who wish to install it on existing systems.
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-qa/issue/593

Metadata Update from @sumantrom:
- Issue assigned to sumantrom

5 years ago

Metadata Update from @sumantrom:
- Issue tagged with: test days

5 years ago

Metadata Update from @sumantrom:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Log in to comment on this ticket.

Metadata