This is the mail archive of the
mailing list for the binutils project.
Re: Release 2.23
- From: Tristan Gingold <gingold at adacore dot com>
- To: Richard Earnshaw <rearnsha at arm dot com>
- Cc: Matthias Klose <doko at ubuntu dot com>, "nickc at redhat dot com" <nickc at redhat dot com>, binutils Development <binutils at sourceware dot org>
- Date: Wed, 1 Aug 2012 16:35:11 +0200
- Subject: Re: Release 2.23
- References: <EFF1B4C0-3885-4580-8DA9-23540D588E9E@adacore.com> <50183FF0.firstname.lastname@example.org> <975FAACC-5CF5-4426-80A5-AB11F995A1F3@adacore.com> <email@example.com>
On Aug 1, 2012, at 4:02 PM, Richard Earnshaw wrote:
>> As it might change the schedule, I'd like to understand the reasons for having aarch64 in 2.23
> Because binutils is a key enabler and rolling this out into various
> distros is significantly harder if it isn't in a major release. In
> particular we're targetting GCC-4.8 for the main compiler support and
> that needs a binutils that supports it.
Looks like a good rational, but this opens other possibilities:
* would it be acceptable to add aarch64 only in 2.23.1 (in case the submission takes time) ?
* if aarch64 comes only with 2.24, what would be the ideal schedule for the release ?
> Why are we planning a binutils release so much earlier this year than we
> have done for the previous 3 or 4 years (at least)?
I plan a release when the trunk is relatively quiet and when I have enough time for it.
Traditionally, the major release is planed for end of summer but we often slip a while :-)