|LTS vs non-LTS makes sense for software, Iâm not sure it really makes sense for a spec. I mean if Iâm using an API implemented by 20 servers isnât it the implementations support statement that is relevant?|
Maybe we should move to a model of LTS releases like OpenJDK? Sets a specific expectation with users that some versions are more "experimental" than others.
Now maybe this has already been discussed on the spec committee - I'm way behind on emails so cannot say for sure.
And even worse: we would break backward compat with every Jakarta EE release :(
> Am 10.05.2019 um 14:33 schrieb David Blevins <dblevins@xxxxxxxxxxxxx>:
>> On May 10, 2019, at 8:55 PM, Richard Monson-Haefel <rmonson@xxxxxxxxxxxxx> wrote:
>> In the github proposal for Incremental, it says over and over again that the result would be mixed namespaces. But the Big Bang never says that yet it does say "Any packages not moved from javax to jakarta could be included in Jakarta EE, but would be forever frozen and never move to the jakarta namespace." which is exactly the same thing, right?
> Here's where they're the same:
> Jakarta EE 9 comes out and it is some mix of javax and jakarta. You must learn the mix.
> Here's where they're different:
> Big Bang: Jakarta EE 10 comes out. You already learned the mix, you're good.
> Incremental: Jakarta EE 10 comes out. Forget the old mix, learn the new one. Also update your source code again.
> And worse case...
> Big Bang: Jakarta EE 11 comes out. You already learned the mix, you're good.
> Incremental: Jakarta EE 11 comes out. Forget the old mix, learn the new one. Hope you have any chance of keeping it straight. Hope your boss doesn't get mad when you tell her you have to migrate source again to use a new feature.
> jakartaee-platform-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
jakartaee-platform-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit