On Wed, Nov 3, 2021 at 3:48 PM Brandon Nielsen <nielsenb@jetfuse.net> wrote:
On 11/3/21 6:31 AM, Kamil Paral wrote:
During the F35 release cycle, there was a dissatisfaction that we use the "basic functionality" criterion [1] too broadly when discussing package manager issues (like multiple issues in plasma-discover). I was asked in the latest QA meeting to propose a specific criterion to cover package managers in detail. Here it is.

Please note that we already have package management partly covered in the Basic criteria [2] and Beta criteria [3]. Please read those first, including footnotes. The following new criterion is proposed against the Final milestone:

~~~~~~~~~~
The default graphical package manager for a given software type must appropriately:

Should this read "for a given release type"? "Software type" feels ambiguous.


"Software type" is defined at [2], and the criteria from [2] and [3] use the same phrasing. (See my original mail for link references). I'm not opposed to changing all occurrences of this, if we have a better term :-)
 

* install, remove and update software, even if multiple operations are scheduled sequentially or concurrently
* list software installed on the system
* list available software (possibly in categories, a curated list, etc)
* display metadata relevant to the selected software (e.g. the description, screenshots, the size)
* start the selected installed software

Should they all really function as launchers as well? I know GNOME's does, not sure how common that is across the board.


Both GNOME Software and KDE Discover provide that functionality. I think the idea is that you hit Install, and then you hit Launch/Open, instead of searching for the new launcher in your system menu. It's good for trying out different apps, etc.

If the button is there, it should work, in my opinion.
 

Looks really good otherwise.

Thanks.