Dear Chris & Adam:

I have an i686 - 32 bit computer for a long time an it works fine for me. Are you perhaps suggesting that I have to throw my old Camaro for a new Rolls Royce? I'm using my computer since Fedora 4 came on an now it has Fedora 23 Workstation. Along those releases I noticed that there are some problems that goes from release to release without fixing  them. Only to shoe one example: I tried to run fedora-easy-karma on may f23 and I have this message: Line 47 import yum. It is supposed that yum is deprecated and in no more on f23+. This bug was reported last year when f22 was  still alive, now on 2016, no one cares about it. Who is supposed to fix that bug?

Francisco Villavicencio.

On Thursday, January 28, 2016 7:43 PM, Chris Murphy <> wrote:

On Thu, Jan 28, 2016 at 1:01 PM, Adam Williamson
<> wrote:

> 1) just ditch the i386 columns entirely; openQA can continue testing
> it, and people can test manually if they want, but we don't bother
> tracking the results in the validation pages

How about option 1. That leaves x86_64 and ARM only; and then where
appropriate the distinction between BIOS and UEFI.

Next, duplicate that page, deleting ARM and UEFI, and changing x86_64
and BIOS to i686. i.e., a 32-bit x86 only specific page.

At least it's available. And it might give us some gauge of
interest/activity in testing 32-bit?

I don't know how wide spread the 32-bit being dropped news has spread,
so it may turn out there will be a 32-bit SIG+spin that shows up one
more release. My understanding is releng doesn't have the time to just
axe all of i686 this cycle, so all of it is going to get built. I
think it's best to do the least amount of work now, that makes it
possible to support a hypothetical 32-bit SIG+spin to do the testing
they'd need to do, to have a quality release. Because it will be
released, and it'll be from Fedora.

Is that reasonable?

I even think it's reasonable if you just went with option 1; noting
the derived page as I've described is offered if/when i686 interested
persons show up to the testing party. Honestly if no one asks (and I'm
not asking for it), then that pretty much tells us at least the
testing state of i686.

Chris Murphy