Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-dev] BigSur fixes for M3
This problem seems a lot like how new Java versions are supported with Y-builds (is that the correct name for them?). IIUC In that case only JDT is updated and made available on the marketplace. Instead of having the bar of re-building the entire stack, can these fixed be rolled out to marketplace or even added as new children in simrel's composite so that check for updates gets the fixes?

I am aware that the above is a technical solution and still would require people to volunteer to do the actual work - and sorry if this is revisiting previously discussed issues too many times.

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Thu, 19 Nov 2020 at 04:41, akurtakov <akurtakov@xxxxxxxxx> wrote:


On Thu, Nov 19, 2020 at 11:30 AM Mickael Istria <mistria@xxxxxxxxxx> wrote:


On Thu, Nov 19, 2020 at 10:24 AM Becker, Matthias <ma.becker@xxxxxxx> wrote:

But maybe we could simple cherry-pick these fixes to the 4.17 maintenance branch. So it would make it lesser effort for others to build a patched 4.17 on themselves.


That's probably a good compromise. However, IIRC the PMC has to approve such cherry-picking to maintenance.

PMC approval was needed when there were builds from maintenance branches. Since there are no bugs from maintenance branches now I haven't seen PMC approvals for such backports so it's much more free reigns there for committers to do backports.
 
Before we start spending time on it, does anyone here really plan to rebuild 4.17 with those patches for their product? I don't think we should cherry-pick "just in case someone wants it", we need to first have a case to drive that effort and make it profitable-ish enough to distract contributors from ongoing development towards master.
So I suggest anyone who has a real need for it to get in touch with the PMC about it, and maybe even to prepare a series of Gerrit cherry-picked patches targeting the maintenance branch. Otherwise, it's probably better to just not care and keep working on a better 4.18 release.
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev

Back to the top