On Tue, 2016-11-15 at 17:15 +0100, Andreas Tunek wrote:
2016-11-15 8:43 GMT+01:00 Adam Williamson
<adamwill(a)fedoraproject.org>:
> On Tue, 2016-11-15 at 07:35 +0100, Andreas Tunek wrote:
> > If something is in the release criteria I expect the feature to be
> > present in the release. If the feature in question has worked for ~20
> > Fedora releases it is not my first priority to test, unless there is
> > specific communication otherwise, like specific "Mac install testing
> > days" (which to my knowledge there hasn't been).
>
> As a general rule of thumb, stuff that gets tested keeps working. Stuff
> that doesn't breaks. It's why we test stuff.
> --
For me as a user it is really difficult to know what has been tested
and what needs more testing. The test days are really good so you know
what to focus on.
We haven't done an 'installer Test Day' for a while because it's not a
typical fit for a Test Day. Test Days are usually for testing out some
big new feature or major change in a release which is a kind of unitary
thing. We haven't had a single specific pinpointable 'major change' in
the installer for several releases now; rather its behaviour tends to
evolve gradually with smaller changes that land frequently, and changes
to the behaviour of other components it depends upon.
What we *do* have for the installer is release validation testing. We
announce all the release validation testing events to this list, and
the OSX test is listed right there. I have sent out pleas multiple
times this cycle for people to help test all the Alpha/Beta/Final
priority validation tests.
Did these not reach you, or is the process too difficult to follow?
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net