From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: On demoting i586 to "legacy" status Date: Wed, 05 Aug 2020 13:08:08 +0100 Message-ID: <3B847F61-1645-46C6-897A-B455B0E09F2E@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0021394646254269084==" List-Id: --===============0021394646254269084== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello, This is me catching up with my very very long TODO list (i.e. book)=E2=80=A6 We have talked about making it clearer that 32 bit on x86 is no longer a good= choice for users at the telephone conference in May: https://wiki.ipfire.org/devel/telco/2020-05-04 I took on the job to make this clearer on the website in the download section= which I rolled out yesterday: https://www.ipfire.org/download I am not happy with the whole download section at all, but this is what we ha= ve for now. New design is in the works. However, this splits the offered architectures into two sections now: * Primary Architectures (x86_64, arm) * Secondary Architectures (i586, aarch64) i586 will be a primary architecture for all releases that did not have x86_64. Aarch64 is a secondary architecture because Arne wanted it marked as =E2=80= =9Cexperimental=E2=80=9D. We do not exactly know how well it runs on some boa= rds, although we have been using it for quite a long time in the build infras= tructure. I have split the two sections by the =E2=80=9CCloud advert=E2=80=9D in the mi= ddle which promotes Cloud over the secondary arches and makes it clear that s= econdary really means secondary because users will have to scroll a lot to fi= nd i586 now. That does it for me now. I would prefer to keep images on the download page (even for aarch64), becaus= e if we do not make them available like this, what is the point to build them= in the first place? The next steps are adding a warning to the web UI that people who are running= on i586 are running a legacy system now. We will support it, but we will adv= ice against using it until we have only a few users left. Currently i686 stan= ds at 26.75% in fire info, which means we have to convince 20% of our users t= o change. Possible, but not within the next few months. A blog article will h= opefully help. Best, -Michael --===============0021394646254269084==--