Hi, I don't know where the LTS requirement comes from, but my take on this: I think the JDK way looks reasonable. We focus on master, if people want an LTS version, they can step up inside the project and work on the LTS version.
If noone care about LTS, noone will step up and all is good, if someone wants LTS, but is not willing to do the work, bad luck. If people want an LTS and want to work on it together in the project - great. I don't see why a release of an LTS version should happen outside the project. That would not be an Apache NetBeans release and we come dangerously close to Libre NetBeans situation. My cents Matthias Am Mittwoch, den 08.07.2020, 15:10 -0700 schrieb Laszlo Kishalmi: > Dear Community, > > It seems we need a stronger definition of LTS, that was one of the > things that came up at the 12.0 release retrospective. > > Our current policy is to have one LTS per year. we only support the > latest LTS, Support means providing patches for critical issues. > > What ideas/requirements faced up so far: > > * LTS should last long. At least for three years like Ubuntu. It > seems > to me that there is a fear of upgrading. Ideally my colleagues > would > like to get just bugfixes without essential upgrade (Jaroslav > Tulach, Oracle) > * We shall think of not making LTS versions, let those be the pain > of > external distributors (Neil C Smith) > * LTS support shall be overlapping we shall not end the support of > one > LTS right after the next one came out. > * There shall be a quarterly update release, preferably about one > month after the last .x release, if we can do that (that's from > me) > * Maybe something else, I've missed, please add that here... > > My thoughts: > > What I think is we shall let the hands of 11.0 LTS go, as we have > not > promised that it would get supported after 12.0 is out. That was > built > with the old release process. The new pipeline (thanks to Eric) is > more > suitable for releasing updates. My experience with the upcoming 12.0- > u1 > is pretty good so far. > I think we need to announce the end of life of 11.0 LTS as well. > > So I think we can support an LTS for 1.5-2 years with quarterly > (maybe > less frequent) updates, starting form 12.0 beyond that it is > probably > shall be sponsored/maintained by external distributors. (Sponsored > here > would mean, that a PMC member from that distributor shall step up > and > take care of the PR organization and the release process, the > community > still have to vote for it, and the resulting nbm-s are served by the > Apache UC. Maintenance would mean that the whole process could > happen > outside of a fork of the release branch, we won't need to create a > release and, no votes are required, but the resulting nbm-s would be > distributed on the third party distributor specific UC.) > > > What do you think? > > -- > > Laszlo Kishalmi > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
