Fedora 21 Alpha validation test work
by Adam Williamson
Hi, folks.
So, we're scheduled for Alpha TC1 tomorrow. We had a nice happy
co-operative plan where QA and the WGs would collaborate on revising the
release validation test process for Fedora.next...
...which, well, didn't really happen. As of this morning we were nowhere
near having a viable validation process. So I went for plan B: I spent
today more or less pulling the entire thing out of my ass.
It's a bit rough around the edges, but I think we more or less have
something workable now. I have skipped the draft stage for a lot of
documents just in the interest of having something vaguely workable in
time for TC1; of course, the pages can be revised as much as necessary
as we work with them.
It's a bit hard to remember everything I've done, but we now have a
draft Alpha Release Criteria page which should cover all
release-blocking media, which for now I'm assuming includes the
Workstation live media, Server minimal and offline install media, Cloud
and ARM disk images, and possibly some kind of generic network install
image. That draft is at
https://fedoraproject.org/wiki/User:Adamwill/Draft_F21_Alpha_criteria
and is based on the stuff from
https://fedoraproject.org/wiki/User:Adamwill/Draft_server_release_criteria , https://fedoraproject.org/wiki/User:Adamwill/Draft_workstation_release_cr... and https://fedoraproject.org/wiki/User:Roshi/QA/Cloud_Docs/Cloud_Alpha_Relea... , plus some adjustments to the templates that handle the preamble.
We have a new validation matrix, for Server product-specific tests:
https://fedoraproject.org/wiki/QA:Server_validation_results_template
The Desktop matrix has been adjusted to cover - not quite elegantly, but
at least cover - both the Workstation product and the KDE spin:
https://fedoraproject.org/wiki/QA:Desktop_validation_results_template
The Base matrix has been extended to add a couple of new test cases that
came out of the Product criteria drafting process, but actually aren't
really product specific, and has had its columns adjusted to be
product-y:
https://fedoraproject.org/wiki/QA:Base_validation_results_template
The installation matrix has similarly had a couple of new criteria
wedged in, but much more importantly, I ripped the netinst, DVD and live
image 'sanity test' sections and replaced them with an ARM-style table
where a single 'generic' test case is run against several images on
several platforms - that's the "Default boot and install" section, so
please cast an eye over it:
https://fedoraproject.org/wiki/QA:Fedora_21_Install_Results_Template
and I made a small change to the release validation test event SOP to
list the server matrix as one to create:
https://fedoraproject.org/wiki/QA/SOP_Release_Validation_Test_Event
Here are links to all (I think) of the new test cases I had to write as
I went along:
https://fedoraproject.org/wiki/QA:Testcase_Boot_default_install
https://fedoraproject.org/wiki/QA:Testcase_kickstart_user_creation
https://fedoraproject.org/wiki/QA:Testcase_base_service_manipulation
https://fedoraproject.org/wiki/QA:Testcase_base_selinux
https://fedoraproject.org/wiki/QA:Testcase_Server_firewall_default
https://fedoraproject.org/wiki/QA:Testcase_kickstart_firewall
https://fedoraproject.org/wiki/QA:Testcase_Server_cockpit_default
The following test cases already existed, but are newly included in the
release validation process (they were written for test days):
https://fedoraproject.org/wiki/QA:Testcase_FreeIPA_realmd_join
https://fedoraproject.org/wiki/QA:Testcase_realmd_join_kickstart
https://fedoraproject.org/wiki/QA:Testcase_realmd_join_server
There are still quite a few i's to dot and t's to cross. There are some
release criteria and test cases that explicitly reference 'the DVD'
image that will need to be adjusted. We need to apply the 'associated
release criterion' template to all the new test cases, and probably
clean up some categorizations. Various other process documentation pages
may need to be updated, we'll have to check through all of them. But I
think now we at least have the broad strokes of what's needed for .next
validation testing.
All feedback on the above changes is of course welcome! Please do cast
your eye over and point out anything I missed, anything that looks
silly, any possible improvements and so on. Remember, though, this is
really *test process* design: we're not actually doing product design
here, if you think there are issues with the Fedora.next changes
themselves, that goes to the WGs or FESCo. As far as this work is
concerned, we're just trying to test the new Products as they're
designed (all of the above is based off of the Product PRDs and tech
specs).
I'll take time tomorrow to do some polishing, and of course look at any
and all feedback on the stuff I did today.
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
8 years, 10 months
Workstation WG Recap 2014-Dec-17
by Paul W. Frields
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2014-12-17/workstation.20...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2014-12-17/workstation.20...
Log: http://meetbot.fedoraproject.org/fedora-meeting/2014-12-17/workstation.20...
* * *
======================================
#fedora-meeting: Fedora Workstation WG
======================================
Meeting started by stickster at 16:00:18 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-12-17/workstation.20...
.
Meeting summary
---------------
* Roll call! (stickster, 16:00:27)
* Surprise topic: F21 (stickster, 16:04:28)
* F21 Workstation is out, it's awesome, and congrats to everyone. That
is all. (stickster, 16:05:47)
* Change proposals (stickster, 16:06:12)
* Current Change checkpoint is proposed for 2015-Jan-20, so about 2.5
or 3 weeks after holiday (stickster, 16:08:27)
* ACTION: mclasen file gnome-shell + nautilus related changes
(stickster, 16:11:45)
* ACTION: stickster Put remaining Change items on agenda for
2015-Jan-07 to check outlook for landing (stickster, 16:12:16)
* LINK: http://fedoraproject.org/wiki/Releases/22/Schedule and
https://wiki.gnome.org/ThreePointFifteen if anyone else wants to
compare (kalev, 16:14:47)
* Current GNOME 3.16 schedule looks like a tight but workable fit for
current Fedora 22 proposed schedule (stickster, 16:15:24)
* jwb points out that some upstream stuff will require Fedora-specific
work outside the WG, e.g. app bundles (stickster, 16:27:01)
* Current big-picture, more Fedora-WS-oriented improvements: (1) app
bundles (high effort, multi-release); (2) upgrade notifications
(lower effort, maybe F22 doable) (stickster, 16:45:25)
* ACTION: mclasen dig up summary/details on current app bundles effort
so we can understand state upstream (stickster, 16:46:00)
* ACTION: mclasen look for mockups for UI portion of upgrade
notification (possibly execution?) (stickster, 16:46:34)
* For reference, a different implementation of upgrades:
https://wiki.gnome.org/Design/OS/Migration (stickster, 16:48:18)
* Resolving firewall question (stickster, 16:49:32)
* ACTION: stickster mclasen be around for FESCo meeting in ~1 hour if
this topic comes up (stickster, 17:03:58)
* ACTION: stickster start discussion on desktop@ list toward a wiki
page that covers our assumptions, problem statement, and our ideal
Workstation approach for firewall (stickster, 17:05:07)
* All other business (stickster, 17:05:28)
* ACTION: stickster Carry over bug triage topic for next meeting
(stickster, 17:05:37)
Meeting ended at 17:07:25 UTC.
Action Items
------------
* mclasen file gnome-shell + nautilus related changes
* stickster Put remaining Change items on agenda for 2015-Jan-07 to
check outlook for landing
* mclasen dig up summary/details on current app bundles effort so we can
understand state upstream
* mclasen look for mockups for UI portion of upgrade notification
(possibly execution?)
* stickster mclasen be around for FESCo meeting in ~1 hour if this topic
comes up
* stickster start discussion on desktop@ list toward a wiki page that
covers our assumptions, problem statement, and our ideal Workstation
approach for firewall
* stickster Carry over bug triage topic for next meeting
Action Items, by person
-----------------------
* mclasen
* mclasen file gnome-shell + nautilus related changes
* mclasen dig up summary/details on current app bundles effort so we
can understand state upstream
* mclasen look for mockups for UI portion of upgrade notification
(possibly execution?)
* stickster mclasen be around for FESCo meeting in ~1 hour if this
topic comes up
* stickster
* stickster Put remaining Change items on agenda for 2015-Jan-07 to
check outlook for landing
* stickster mclasen be around for FESCo meeting in ~1 hour if this
topic comes up
* stickster start discussion on desktop@ list toward a wiki page that
covers our assumptions, problem statement, and our ideal Workstation
approach for firewall
* stickster Carry over bug triage topic for next meeting
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* stickster (103)
* jwb (53)
* mclasen (48)
* cschalle_ (10)
* ryanlerch (9)
* kalev (9)
* randomuser (7)
* rdieter (5)
* zodbot (5)
* mcatanzaro (2)
* jreznik (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
Paul W. Frields http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
http://redhat.com/ - - - - http://pfrields.fedorapeople.org/
The open source story continues to grow: http://opensource.com
8 years, 11 months
Application is ready notification
by Ryan Lerch
Just wondering if anyone here knows of the design rationale for the
(seemingly intermittent to me) notification i get informing me that an
application window is ready for my attention.
I seem to get these most when opening a file in the default application
from firefox, or opening an application from the terminal, or sometimes
when clicking on a notification from an application. In all cases when I
see this notification, I did want to see the application window to
appear and get focus.
There is a shell extenstion available to turn off this application is
ready behaviour, which I do use, but IMO, this would be a useful default
behaviour to have turned on in Workstation.
cheers,
ryanlerch
8 years, 11 months
Feature Idea: provide a graphical way to upgrade to F22 workstation
by Ryan Lerch
Hi all,
One thing i didnt see on the roadmap, but would be definitely useful for
our users would be a way to notify users that a new version of Fedora
Workstaion is available, and provide an easy way for them to kick of a
fedup upgrade without having to use the command line.
One other thing that might be useful here is a notification for users
telling them when the version they are using is going EOL, and that no
more updates will be provided for their version, and then providing them
the same GUI to upgrade.
cheers,
ryanlerch
8 years, 11 months
Sevices don't start with boot (FD21 Desktop)
by Peter Laursen
I think this happened with some recent updates.
I experience that "sshd" and "mysqld" (MariaDB 10.0.14) services don't
start automatically after reboot when started with "service" or "systemctl"
commands. I will need to manually execute "systemctl enable name.service"
(what will create the necessary symlink, and services will start with next
reboot).
Is this intended?
Also there is an inconsistence between the default Gnome edition and the
Xfce 'spin' here. On Xfce both mentioned services were affected. On Gnome
mysqld was not affected but sshd was (as far as I remember - it could be
opposite, but I think I remember right!).
--
Hilsen / Regards
Peter Laursen
8 years, 11 months
F21 32bit live-dvd goes into hibernation
by Donald Buchan
I've installed F21 64bit on my new, fresh out of the box Dell desktop.
Things are going great! (And, nuking Windows was satisfying.)
Now I'm trying to install F21 32-bit on my Acer Aspire One Netbook
D150-1055 single core 1.6GHz Atom Processor N270 2gig memory 160gig HD
laptop, using an LG portable super multi drive usb-dvd.
The images I've used are F21 workstation 32bit downloaded on 09 december
2014 and burned using F19 and dvd drive above, using CD/DVD creater,
then I re-downloaded the iso on 14 december 2014 and burned it on an
integrated dvd writer on my new dell machine running F21 workstation
64bit using brasero.
Both times my Aspire One kept on going in hibernation during the initial
bootup of the live-DVD of F21 workstation 32bit. I get about three
quarters of the way through the white tear drop startup screen and the
hibernation begins. Hitting any key wakes up the machine and things will
continue, and the hibernation keeps on occuring after about a minute,
and I keep on waking up the machine. This cycle keeps on occuring once I
get to the initial screen offering to run the live-dvd or install to the
HD. This is all while trying to boot up the live dvd and head directly
into the installation process.
No, I have not been playing with the power settings -- in fact, this
begins occuring during the bootup. Yes, the clamshell was fully open.
No, the power cord was not faulty. No, I was not running on battery with
low power -- in fact, I usually operate on electricity with the battery
pack out, and this never causes any problems. The unit is perfectly
stable with Fedora 19 and has always been since I first installed linux
on it with Fedora 11 in 2009, and has never had problems with Fedora 11,
12, 14, 15, 17, and 19.
Is anyone else having a similar problems with the live-dvd for F21
suddenly always going into hibernation on a similar machine or other
laptop?
Thank you
8 years, 11 months