On 1/8/19 5:06 AM, Lukas Ruzicka wrote:
* The list of pre-installed applications could be pruned of those
which don't make much sense for that particular purpose (e.g. CD
writing software on ARM, or perhaps on any system nowadays).
Certainly a good thing to do.
* Pre-installed applications could be deduplicated where possible
(e.g. not having several web browsers pre-installed by default).
* We could define a list of "important" applications that would be
tested thoroughly and the basic functionality criterion would apply
just to them. That would tell QA where to focus. (This would
obviously contain applications like system settings, file browser,
text editor, browser, terminal emulator, etc. But e.g. a screenshot
utility would probably not fall into the list. Also, in case of
duplicated apps, only one of those could be marked as "important",
and the others would* not). The rest of the applications would be
just best effort in terms of QA, and wouldn't block the release.
Addressing both points together -
I believe we are decent with not having too many duplicates on Xfce (not
sure about other DEs). One approach I can think of is testing only those
in the primary group in comps. In the case of Xfce, the live ISO has
packages from both xfce-desktop and xfce-apps group. Perhaps, we can
limit QA testing to only the primary group.
Of course, this would need bit more organization from the spin
maintainers side since some "important" applications are in xfce-apps
(e.g. firefox) but we (xfce maintainers) can do that.
* Last but not least, you could help us more with release
validation
before relevant milestones (Beta, Final) :-) If there's anything
that should be improved on our part (communication, instructions,
etc), we'd love to hear that.
We (to be clear - I am not blaming anyone) did drop the ball on Xfce
testing in F29 cycle. Hopefully, we can avoid this moving forward.
My two cents.
Mukundan.