Release criteria proposal: installing / removing software
by Adam Williamson
Hi, folks!
It's been noted a few times before that we have a release criterion
that requires *updating* packages (or, these days, 'software', to cover
things like modules) to work...but we don't have criteria covering
other basic software management tasks, notably installing and removing.
There is a possible justification for this: so long as update works,
bugs in installation and removal can be fixed with updates. But really,
it seems reasonable to me that we should require basic
installation/removal of packages (and modules, and anything else we may
choose to consider release critical now or in future, e.g. flatpaks,
Shell extensions...) to work on release.
So, I'm proposing we modify the existing Basic and Beta criteria that
cover only updates, to also cover installation and removal. I like this
a bit more than adding separate criteria as the footnotes would be very
similar, and combining allows the footnotes to be shared.
So, the Basic criterion would change from:
"The installed system must be able to download and install appropriate
updates with the default console tool for the relevant update type
(e.g. default console package manager)."
to:
"The installed system must be able to install, remove, and install
appropriate updates for software with the default console tool for the
relevant software type (e.g. default console package manager). This
includes downloading of packages to be installed/updated."
the Beta criterion would similarly change from:
"The installed system must be able to download and install appropriate
updates with the default tool for the relevant update type in all
release-blocking desktops (e.g. default graphical package manager)."
to:
"The installed system must be able to install, remove, and install
appropriate updates for software with the default tool for the relevant
update type in all release-blocking desktops (e.g. default graphical
package manager). This includes downloading of packages to be
installed/updated."
the footnotes would be tweaked to refer more generically to 'software'
and stuff instead of 'updates', just kinda logical changes to reflect
the broadened criterion; I can go into detail on that if anyone wants.
Obviously if the criterion change is agreed upon, we will add test
cases to the test matrices.
Thoughts, comments, suggestions, acks and nacks? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
4 years, 8 months
Workstation WG meeting recap 2018-June-18
by mcatanzaro＠gnome.org
Hi,
I forgot to send the meeting recap from Monday's WG meeting.
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-06-18/workstation...
Minutes (text):
https://meetbot-raw.fedoraproject.org/fedora-meeting-2/2018-06-18/worksta...
Log:
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-06-18/workstation...
==============================
#fedora-meeting-2: workstation
==============================
Meeting started by mcatanzaro at 13:00:15 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-06-18/workstation...
.
Meeting summary
---------------
* roll call (mcatanzaro, 13:00:26)
* VS Code repo as external repo (mcatanzaro, 13:08:34)
* LINK: https://pagure.io/fedora-workstation/issue/52 (mcatanzaro,
13:08:38)
* PyCharm repo doesn't work (mcatanzaro, 13:10:46)
* LINK: https://pagure.io/fedora-workstation/issue/55 (mcatanzaro,
13:10:49)
* ACTION: cschalle to follow up with repo maintainer (mcatanzaro,
13:14:47)
* firefox-wayland desktop file (mcatanzaro, 13:15:21)
* LINK: https://pagure.io/fedora-workstation/issue/59 (mcatanzaro,
13:15:25)
* Wayland remoting (mcatanzaro, 13:20:52)
* LINK: https://pagure.io/fedora-workstation/issue/60 (mcatanzaro,
13:20:56)
* LINK: https://fedoraproject.org/wiki/Packaging:DefaultServices
(sgallagh, 13:25:14)
* ACTION: : mclasen to file a bz for the pipewire socket activation
change (mclasen, 13:31:38)
* ACTION: : kalev to add gnome-remote-desktop to comps (mclasen,
13:32:56)
* : open floor (mclasen, 13:33:07)
* LINK: https://pagure.io/fedora-workstation/issue/61 (cschalle,
13:33:20)
* ACTION: cschaller/mclasen to find a packager for the gpu governor
tool thing (mclasen, 13:51:11)
Meeting ended at 13:52:16 UTC.
Action Items
------------
* cschalle to follow up with repo maintainer
* : mclasen to file a bz for the pipewire socket activation change
* : kalev to add gnome-remote-desktop to comps
* cschaller/mclasen to find a packager for the gpu governor tool thing
Action Items, by person
-----------------------
* cschalle
* cschalle to follow up with repo maintainer
* cschaller/mclasen to find a packager for the gpu governor tool thing
* kalev
* : kalev to add gnome-remote-desktop to comps
* mclasen
* : mclasen to file a bz for the pipewire socket activation change
* cschaller/mclasen to find a packager for the gpu governor tool thing
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mclasen (43)
* mcatanzaro (40)
* cschalle (35)
* kalev (11)
* zodbot (10)
* ryanlerch (8)
* sgallagh (7)
* rdieter (6)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 9 months
can we get some text on the page where people used to set their
passwords?
by Matthew Miller
I'm seeing a number of user help requests where there's confusion about
not being prompted for a password. Can we change that screen so instead
of saying "configuration", it has some information about the first
login configuration?
Maybe this screen could change to have more room for the "banners", and
we could update them?
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
4 years, 9 months
Workstation WG meeting recap 2018-June-04
by Owen Taylor
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-06-04/workstation...
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-06-04/workstation...
Log:
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-06-04/workstation...
=================================
#fedora-meeting-2: Workstation WG
=================================
Meeting started by otaylor at 13:00:38 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting-2/2018-06-04/workstation...
.
Meeting summary
---------------
* Roll call (otaylor, 13:00:57)
* pycharm repository (otaylor, 13:07:11)
* vscode as 3rd party repository
(https://pagure.io/fedora-workstation/issue/52) (otaylor, 13:09:00)
* ACTION: cschalle will follow up on the pycharm and vscode 3rd party
repositories and report back in 2 weeks (otaylor, 13:20:09)
* Need an end-user docs / wiki page for Third Party Repositories -
https://pagure.io/fedora-workstation/issue/41 (otaylor, 13:20:54)
* open floor (otaylor, 13:23:24)
* AGREED: the workstation working group supports the move to hiding
the grub menu by default (+5;0;0) (otaylor, 13:44:20)
* LINK:
https://www.redhat.com/archives/libosinfo/2018-June/msg00007.html
(mclasen, 13:49:55)
* silverblue will show up in gnome boxes list of install options soon,
it is being added to libosinfo as a separate item (otaylor,
13:52:28)
Meeting ended at 13:55:35 UTC.
Action Items
------------
* cschalle will follow up on the pycharm and vscode 3rd party
repositories and report back in 2 weeks
Action Items, by person
-----------------------
* cschalle
* cschalle will follow up on the pycharm and vscode 3rd party
repositories and report back in 2 weeks
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* otaylor (51)
* mclasen (22)
* zodbot (13)
* cschalle (11)
* juhp (7)
* ryanlerch (5)
* linuxmodder (1)
* x3mlinux (1)
* rdieter (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 9 months
