Re: Release criteria proposal: first boot experience

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Sep 1, 2020 at 10:24 PM Michael Catanzaro <mcatanzaro@xxxxxxxxx> wrote:
Hi,

We currently have a bug where the Online Accounts page in initial setup
is nonfunctional. [1] This doesn't violate any current release
criterion, but surely we don't want to release with a broken initial
setup experience. So let's add a new requirement for that. How about
something like:

"If an initial setup utility is run or intended to be run after the
first boot of the installed system, then it must start successfully and
each page or panel of the initial setup utility should withstand a
basic functionality test."

OK that's pretty basic, but it gets the point across. I think this can
be a final requirement, not necessarily important enough to be a beta
requirement. Bikeshed away!

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1870476

Hey Michael,
all criteria proposals should definitely (also) go to the test list, adding into CC.

Just to put everyone on the same page, we already have this Basic criterion:
"A system installed with a release-blocking desktop must boot to a log in screen where it is possible to log in to a working desktop using a user account created during installation or a 'first boot' utility."

That means that user creation is already guaranteed to be functional (but might be rough around the edges). Of course that doesn't cover any other actions available in the initial setup. Therefore your proposal (targeting the Final milestone, which seems sensible) makes sense in this regard.

There are the screens in the initial setup:
1. Welcome
2. Privacy (Location Services, Automatic Problem Reporting)
3. Online Accounts (Google, Nextcloud, Microsoft, Facebook)
4. About You (Name, Username, Enterprise Login)
5. Password
6. Done

Since every screen contains just a couple of things, the "basic functionality test" as you phrased it seems to cover essentially everything that is present in there, with one arguable exception of the Enterprise Login functionality. Do you have the same impression?

This will also cover the other initial setup screen that is visible for KDE and other desktops (does it run also for ARM text installs? I'm not sure). That one contains:
1. User Creation (Name, Username, Password, Make admin, Advanced)
And that was all (at least for my KDE install during which I didn't create a regular user).

Overall I find the criterion reasonable and useful and I'm +1 to incorporating it. Its current phrasing seems fine to me.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux