From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] ARM64 and Debian LTS
Date: Wed, 18 Apr 2018 15:47:10 +0100 [thread overview]
Message-ID: <1524062830.2587.7.camel@codethink.co.uk> (raw)
In-Reply-To: <3200087.i7ITxrmn3d@linux-if6s>
On Mon, 2018-04-16 at 17:07 +0200, Agust?n Benito Bethencourt wrote:
> Hi,
>
> On Monday, 16 April 2018 16:23:19 CEST Jan Kiszka wrote:
> > On 2018-04-16 15:52, Agust?n Benito Bethencourt wrote:
> > > Hi Ben,
> > >
> > > is there any discussion going on about when ARM64 can make it as supported
> > > architecture? Is it something expected for 2019 or is it not on the
> > > roadmap
> > > yet?
> >
> > /me confused: https://wiki.debian.org/SupportedArchitectures and
> > https://www.debian.org/ports/#portlist-released list arm64 as supported
> > already.
>
> Sorry, referred to LTS supported architecture.
The list of architectures for jessie LTS is not decided and I haven't
seen any discussion of it yet. The starting point for discussion would
be the list of architectures included in Debian 7 LTS, and that didn't
include arm64 because it wasn't in Debian 7 to start with.
I think that a proposal to include arm64 in Debian 8 LTS would probably
be accepted. There should be no practical issues with maintaining the
infrastructure for it as arm64 hardware is only becoming more easily
available.
So I suggest that the interested organisations speak up on the debian-
lts mailing list. For reference, here's the discussion of adding armel
and armhf back in 2016:
<https://lists.debian.org/debian-lts/2016/04/msg00045.html>. Note in
particular that there is some sensitivity about companies paying for
development work while being "free-riders" on Debian infrastructure.
These organisations should consider sponsoring Debian, or pledging to
contribute development or testing effort directly, instead of or as
well as paying Freexian or other contractors working on Debian LTS.
Ben.
--
Ben Hutchings
Software Developer, Codethink Ltd.
next prev parent reply other threads:[~2018-04-18 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 13:52 [cip-dev] ARM64 and Debian LTS Agustín Benito Bethencourt
2018-04-16 14:23 ` Jan Kiszka
2018-04-16 14:34 ` Wolfgang Mauerer
2018-04-17 6:43 ` Zoran S
2018-04-16 15:07 ` Agustín Benito Bethencourt
2018-04-18 14:47 ` Ben Hutchings [this message]
2018-04-18 17:29 ` Florian Weimer
2018-04-19 12:04 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1524062830.2587.7.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox