Hi Mickael,
The fix is likely small and riskless, and I’ll try to contribute something but I’ll probably not get to that before Friday due to other priorities (and after RC2 it’s really getting late).
I understand that the dev team has to put priorities in place (on the reference platforms). On the other hand, the plan also says “we expect that Eclipse works fine on other current
Java VM and OS versions”. I don’t even see a minimum GTK version explicitly mentioned in the plan (like we had in earlier plans). And I do think that especially in the enterprise world with its slow adoption cycles, having REL6 supported would still be
a significant asset in terms of community adoption.
Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind
River
From:
"platform-releng-dev-bounces@xxxxxxxxxxx" <platform-releng-dev-bounces@xxxxxxxxxxx> on behalf of "mistria@xxxxxxxxxx" <mistria@xxxxxxxxxx>
Reply-To: "Eclipse list." <platform-releng-dev@xxxxxxxxxxx>
Date: Tuesday 23 May 2017 at 17:52
To: "Eclipse list." <platform-releng-dev@xxxxxxxxxxx>
Subject: Re: [platform-releng-dev] M7/RC1 Regression: Launcher fails on RHEL6
So I guess it's relatively fine to see such issues in RHEL6, even that late. And even if you fix a few of them, the fact that it's not supported makes that it's likely that you face some other issues on RHEL6.
That said, if you can provide patches that widens the compatibility range without reducing quality or increasing maintenance effort, there is probably no reason to refuse those.