[arch-dev-public] News draft for i686 deprecation
Finally found some time to write a draft for news post on i686. Here it is: Title: i686 is dead, long live i686 Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture. The decision means that February ISO will be the last that allows to install 32 bit Arch Linux. The next 9 months are deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging and repository tools will no longer require that from maintainers, effectively making i686 unsupported. However, as there is still some interest in keeping i686 alive, we would like to encourage the community to make it happen with our guidance. Depending on the demand, an official channel and mailing list will be created for second tier architectures. - Any suggestions? Bartłomiej
2017-01-23 15:58 GMT+01:00 Bartłomiej Piotrowski <bpiotrowski@archlinux.org> :
However, as there is still some interest in keeping i686 alive, we would like to encourage the community to make it happen with our guidance. Depending on the demand, an official channel and mailing list will be created for second tier architectures.
Please put an e-mail address here, where potential contributors could send their applications. Or even create a mailing list for that before publishing this news. -- György Balló Trusted User
On 2017-01-23 17:05, Balló György via arch-dev-public wrote:
Please put an e-mail address here, where potential contributors could send their applications. Or even create a mailing list for that before publishing this news.
What I infer from my conversation with Allan is that neither of us is interested in leading this personally. Will you take on this role? If Florian has no issues with it, I'm completely fine with creating a list and channel beforehand. Bartłomiej
On 23.01.2017 22:09, Bartłomiej Piotrowski wrote:
If Florian has no issues with it, I'm completely fine with creating a list and channel beforehand.
I don't mind creating those, but we already have an arch-ports list[1]. Maybe it's a good idea to revive that? [1] https://lists.archlinux.org/listinfo/arch-ports Florian
On 2017-01-24 07:28, Florian Pritz via arch-dev-public wrote:
On 23.01.2017 22:09, Bartłomiej Piotrowski wrote:
If Florian has no issues with it, I'm completely fine with creating a list and channel beforehand.
I don't mind creating those, but we already have an arch-ports list[1]. Maybe it's a good idea to revive that?
[1] https://lists.archlinux.org/listinfo/arch-ports
Florian
Right, I completely forgot about this list. Sounds good to me. I just registered #archlinux-ports on Freenode (I'm happy to expand the list of owners later). Bartłomiej
On 24/01/17 07:09, Bartłomiej Piotrowski wrote:
What I infer from my conversation with Allan is that neither of us is interested in leading this personally.
FYI, I will provide advise/mentorship to any team that forms to continue this, but definitely can not take on leading it. A
2017-01-23 22:09 GMT+01:00 Bartłomiej Piotrowski <bpiotrowski@archlinux.org> :
What I infer from my conversation with Allan is that neither of us is interested in leading this personally. Will you take on this role?
I'm not sure about that, but I would like to keep i686 alive. I have some ideas and plans about secondary architectures and automated builds, and I want to work on implementing this, but it needs a team and an infrastructure. -- György Balló Trusted User
Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture. The decision means that February ISO will be the last that allows to install 32 bit Arch Linux. The next 9 months are deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging and repository tools will no longer require that from maintainers, effectively making i686 unsupported. However, as there is still some interest in keeping i686 alive, we would like to encourage the community to make it happen with our guidance. The [archlinux-ports][1] mailing list and Freenode IRC channel will be used for further coordination. [1]: https://lists.archlinux.org/listinfo/arch-ports
On 25 January 2017 at 08:54, Bartłomiej Piotrowski <bpiotrowski@archlinux.org> wrote:
Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture.
The decision means that February ISO will be the last that allows to install 32 bit Arch Linux. The next 9 months are deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging and repository tools will no longer require that from maintainers, effectively making i686 unsupported.
However, as there is still some interest in keeping i686 alive, we would like to encourage the community to make it happen with our guidance. The [archlinux-ports][1] mailing list and Freenode IRC channel will be used for further coordination.
I kept up to date a bit with what people around the net are thinking about this draft and it appears there is some confusion as to whether [multilib] will be affected by this. I propose adding the following sentence: "The [multilib] repositories will not be affected by this change."
On 2017-01-25 11:14, Sven-Hendrik Haase wrote:
On 25 January 2017 at 08:54, Bartłomiej Piotrowski <bpiotrowski@archlinux.org> wrote:
Due to the decreasing popularity of i686 among the developers and the community, we have decided to phase out the support of this architecture.
The decision means that February ISO will be the last that allows to install 32 bit Arch Linux. The next 9 months are deprecation period, during which i686 will be still receiving upgraded packages. Starting from November 2017, packaging and repository tools will no longer require that from maintainers, effectively making i686 unsupported.
However, as there is still some interest in keeping i686 alive, we would like to encourage the community to make it happen with our guidance. The [archlinux-ports][1] mailing list and Freenode IRC channel will be used for further coordination.
I kept up to date a bit with what people around the net are thinking about this draft and it appears there is some confusion as to whether [multilib] will be affected by this. I propose adding the following sentence:
"The [multilib] repositories will not be affected by this change."
I will include that in the final post news that I want to publish this evening, unless there are more suggestions. Bartłomiej
participants (5)
-
Allan McRae
-
Balló György
-
Bartłomiej Piotrowski
-
Florian Pritz
-
Sven-Hendrik Haase