Community
Participate
Working Groups
I know that the current release cycle is currently 3 months but in the last releases (4.14 and 4.15 as well) we (and others of course) were suffered by https://bugs.eclipse.org/bugs/show_bug.cgi?id=558495 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=561287 I think that due to the fact that there are so many eclipse-users are out there with different projects, platforms, used features, ... it will be nearly impossible to cover all combinations by tests and therefore the chance is relatively high, that many users are affected by a found bug. So it would be really nice if you would consider to provide maintenance releases because switching to I-builds or milestone-releases is not always an option for users/companies.
Please check the discussion in: https://www.eclipse.org/lists/platform-dev/msg02171.html
The discussion doesn't sound very promising. :-( I know that providing additional maintenance-releases means more effort on your side but is it really a good idea to have public releases with critical issues and let the user live for three months with that? In my opinion maintenance releases are at least needed for critical issues like https://bugs.eclipse.org/bugs/show_bug.cgi?id=558495 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=561287 because both of them result in a not working eclipse-version. But to be honest for both issues at least a workaround was found. But depending on the deployment strategy in the companies or the count of developers sometimes souch workarounds will not be a good solution. (I don't remember the exact examples but I've seen such comments in bug-reports).
found an example: https://bugs.eclipse.org/bugs/show_bug.cgi?id=558495#c64
There are no plans to do this. As mentioned on the mailing list you can build from the maintenance branch or ask/pay someone to do it for you.
