This is the mail archive of the
mailing list for the GCC project.
Re: dejagnu version update?
- From: Mike Stump <mikestump at comcast dot net>
- To: Andreas Schwab <schwab at suse dot de>
- Cc: Jeff Law <law at redhat dot com>, Bernhard Reutner-Fischer <rep dot dot dot nop at gmail dot com>, David Malcolm <dmalcolm at redhat dot com>, gcc-patches List <gcc-patches at gcc dot gnu dot org>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Wed, 16 Sep 2015 09:14:16 -0700
- Subject: Re: dejagnu version update?
- Authentication-results: sourceware.org; auth=none
- References: <1441916913-11547-1-git-send-email-dmalcolm at redhat dot com> <1441916913-11547-3-git-send-email-dmalcolm at redhat dot com> <55F720E6 dot 7020709 at redhat dot com> <4CB1399A-23A6-44F7-A25F-ECBD953E03A0 at gmail dot com> <55F74C3D dot 50504 at redhat dot com> <F5F4A096-2DD7-4635-9CB2-5A611247D71F at comcast dot net> <1B14D92A-0476-416B-A80D-A3083383C48D at gmail dot com> <55F879CB dot 2090607 at redhat dot com> <16565ACE-A56C-4971-BEA9-B299C9B40346 at comcast dot net> <mvmfv2eesa5 dot fsf at hawking dot suse dot de>
On Sep 16, 2015, at 12:29 AM, Andreas Schwab <firstname.lastname@example.org> wrote:
> Mike Stump <email@example.com> writes:
>> The software presently works with 1.4.4 and there aren’t any changes
>> that require anything newer.
> SLES 12 has 1.4.4.
Would be nice to cover them as well, but their update schedule, 3-4 years, means that their next update is 2018. They didn’t update to a 3 year old stable release of dejagnu for their last OS, meaning they are on a > 7 year update cycle. I love embedded and really long term support cycles (20 years), but, don’t think we should cater to the 20 year cycle just yet. :-) Since 7 is substantially longer than 2, I don’t think we should worry about it. If they had updated at the time, they would have had 3 years of engineering and testing before the release and _had_ 1.5.