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, 8 months
NTP switch in gnome-control-center is broken
by Michael Catanzaro
Hi,
Let's decide what to do about
https://bugzilla.redhat.com/show_bug.cgi?id=1136905
Long story short: timedated no longer supports NTP clients other than
timesyncd (the new systemd NTP client). Oversimplifying, the chrony
developers say that chrony is better than timesyncd, and the systemd
developers say that timesyncd is better than chrony.
We need to remove chrony from the default install and figure out what to
do for users upgrading to F21 (if we do not uninstall chrony, the switch
will be broken), or patch out the change to timedated, or build systemd
without timedated and provide our own implementation of it, or patch
gnome-control-center.
None of these seem like particularly good options. Removing chrony seems
like an easy solution, but I'm not sure how we could handle upgrades
without hurting users who don't want chrony to be removed.
Michael
8 years, 10 months
systemd-networkd and network management plans
by Rahul Sundaram
Hi
For a long time, NetworkManager handled only wifi and simpler connection
needs and although it now has support for bridging, bonding etc, it seems
not integrated with GNOME very much.
Meanwhile, systemd-networkd handles a lot more of that but doesn't handle
wifi (yet?) and I am not sure what the plans are between NM and
systemd-networkd to avoid code duplication.
Do we still ship the older network scripts in Fedora workstation? What are
the plans to integrate systemd-networkd if any? What is the future of NM?
Rahul
8 years, 11 months
"Package sets" release criterion: what to do with it?
by Adam Williamson
Hi, folks. I'm checking the release criteria again for Fedora.next
compatibility, and there's an Alpha criterion with obvious issues:
"Package sets
When doing a graphical install using the dedicated installer images, the
installer must be able to install each of the release blocking desktops,
as well as the minimal package set. "
This was obviously written to the world where we had generic installer
images - the DVD, and intentionally-generic netinsts. We do not have
those things any more.
Do we want to dump this criterion entirely, or is there any of it we
would like to keep? For instance, would we consider it 'release
blocking' functionality for you to be able to do some/any of the above
from the Server and/or Workstation network install images *after
configuring the repos manually*? Particularly, the minimal installation?
I'm not sure F21 as currently conceived would offer an avenue for doing
an interactive minimal installation.
Basically, it comes down to: do we want to have a blessed method for
doing a network install of KDE and/or minimal? If so, do we want to
block releases on it?
Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
8 years, 11 months
Beta / Final release criteria for Workstation
by Adam Williamson
Hi, folks. I wanted to ask if you envisage a need for release criteria
for Workstation at Beta (or Final) over and above those that already
exist for 'desktop' stuff. Areas I notice:
SSSD is listed in the tech spec. We have server-side requirements for
FreeIPA in the Server product; do we want to formulate client-side
requirements?
We don't really have criteria relating to a11y or complex input methods;
this isn't Workstation-y in particular, but something that might be
interesting?
Appearance is something we'd want to enforce if it were actually done,
but I get the impression the Qt variant of Adwaita isn't actually
written yet.
Functional requirements for the 'core apps' - we have requirements for
graphical updating (but not package install), web browser, and terminal
in the current criteria, but not for text editor, file manager, Boxes,
or 'developer assistant'.
Do remember that anything we write in the release criteria is something
we expect to enforce: if you don't actually want the release to be
delayed if it's not done, best not to have a criterion for it. More
aspirational 'to-do' or 'it'd be good if...' lists can be handled
somewhere else, I don't know/care where, but not in the criteria :)
Thanks folks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
8 years, 11 months
[PATCH] Move captive portal to fedora-release-workstation
by Josh Boyer
Pretty much what we discussed on IRC yesterday. Anyone have problems
with me committing this today?
josh
diff --git a/gnome-shell.spec b/gnome-shell.spec
index a085076..94e284d 100644
--- a/gnome-shell.spec
+++ b/gnome-shell.spec
@@ -102,8 +102,6 @@ Requires: gdm-libs%{?_isa}
Requires: clutter%{?_isa} >= %{clutter_version}
# needed for settings items in menus
Requires: control-center
-# needed for captive portal support
-Requires: NetworkManager-config-connectivity-fedora
%description
GNOME Shell provides core user interface functions for the GNOME 3 desktop,
diff --git a/fedora-release.spec b/fedora-release.spec
index 333875f..1d7db6b 100644
--- a/fedora-release.spec
+++ b/fedora-release.spec
@@ -72,6 +72,8 @@ Requires: fedora-release = %{version}-%{release}
Conflicts: fedora-release-cloud
Conflicts: fedora-release-server
Conflicts: fedora-release-standard
+# needed for captive portal support
+Requires: NetworkManager-config-connectivity-fedora
%description workstation
Provides a base package for Fedora Workstation-specific configuration files to
8 years, 11 months
xfce desktop
by josé Carlos
Hello everybody
I'm a brazilian guy, and it's my first time in a discution list. So, i
already apologize for my english rss
I am coming of debian based distro, so, i am adapting myself to
fedora'usability and package manager.
My doubt is how can i install xfce 4.12 in fedora 20(i install xfce 4.10
and i tried upgrade so i could not.
ps: my fedora is fedora spin mate
Thanks!
*José Carlos F. Jr*
9 years
Workstation WG Meeting Minutes 2014-09-24
by Josh Boyer
=======================================
#fedora-meeting: Workstation WG meeting
=======================================
Meeting started by jwb at 15:00:55 UTC. The full logs are available at
http://meetbot.fedoraproject.org/fedora-meeting/2014-09-24/workstation.20...
.
Meeting summary
---------------
* init (jwb, 15:00:55)
* GNOME Classic in default install (jwb, 15:05:22)
* AGREED: leave Classic included by default. Work with QA to ensure
it gets properly tested (jwb, 15:09:09)
* Target image size (jwb, 15:09:59)
* AGREED: Workstation image size has a soft limit of 1.5GB for F21/F22
(jwb, 15:32:35)
* ACTION: kalev to produce a report of additions/removals compared to
F20 for review (jwb, 15:32:56)
* WG member re-affirmation (jwb, 15:33:09)
* present WG members all wish to remain on the WG. jwb to follow up
with absent members (jwb, 15:41:36)
* discuss open seat on the list (jwb, 15:41:41)
* CUPS (jwb, 15:42:08)
* LINK: https://fedorahosted.org/workstation/ticket/8 (jwb,
15:42:12)
* AGREED: enable CUPS on demand in Workstation (jwb, 15:46:03)
* ACTION: kalev and mclasen_ to follow up with twaugh on
implementation (jwb, 15:46:18)
* open floor (jwb, 15:47:36)
* LINK: https://fedorahosted.org/fesco/ticket/1337#comment:12
(juhp_, 16:03:00)
* ACTION: jwb to follow up with kalev on moving the dependency for
capitve portal to fedora-release-workstation instead of gnome-shell
(jwb, 16:06:40)
Meeting ended at 16:08:23 UTC.
Action Items
------------
* kalev to produce a report of additions/removals compared to F20 for
review
* kalev and mclasen_ to follow up with twaugh on implementation
* jwb to follow up with kalev on moving the dependency for capitve
portal to fedora-release-workstation instead of gnome-shell
Action Items, by person
-----------------------
* jwb
* jwb to follow up with kalev on moving the dependency for capitve
portal to fedora-release-workstation instead of gnome-shell
* kalev
* kalev to produce a report of additions/removals compared to F20 for
review
* kalev and mclasen_ to follow up with twaugh on implementation
* jwb to follow up with kalev on moving the dependency for capitve
portal to fedora-release-workstation instead of gnome-shell
* mclasen
* kalev and mclasen_ to follow up with twaugh on implementation
* mclasen_
* kalev and mclasen_ to follow up with twaugh on implementation
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* jwb (104)
* elad661 (42)
* bitlord (35)
* mclasen_ (32)
* kalev (26)
* otaylor (23)
* juhp_ (21)
* sgallagh (21)
* stickster (13)
* drago01 (8)
* zodbot (7)
* cwickert (5)
* aday (4)
* bochecha (2)
* orc_fedo_ (1)
* ltinkl (0)
* ryanlerch (0)
* juhp (0)
* cschalle (0)
* mclasen (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
9 years
Captive Authentication feature in f21
by Ryan Lerch
Hi all,
Been trying out F21 on my new laptop, and saw the nifty new captive auth
feature when logging into wifi at starbucks this morning.
I did notice that the name of the application (as it appears in the
gmenu up near the activities button) is "Captive Authentication". To a
new user, that may not know exactly what captive auth is, this may be
worrying or confusing -- "what about my authentication is being captured?"
Perhaps changing this to something like "Network Login" work work better?
cheers,
ryanlerch
9 years
Workstation WG 2014-09-24 Meeting Agenda
by Josh Boyer
Hi All,
Meeting tomorrow. Agenda is below. If you have anything to
add/change, please let me know.
* GNOME Classic in default install?
* Target image size?
- See libreoffice thread(s)
- Alpha is 1.3GB
* WG member re-affirmation and replacing Lukáš Tinkl
- I have confirmed with Lukáš that he is OK with stepping down
josh
9 years