Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-docs-dev] Future plans
Yes. Let’s bring Java 11 to Wikitext!

- Leo

On Mar 10, 2022, at 9:16 PM, Aleksandar Kurtakov <akurtako@xxxxxxxxxx> wrote:

Hi Leo,
As 2022-03 is done deal, can we switch master to Java 11 now?

On Tue, Oct 5, 2021 at 8:26 PM Leo Dos Santos <leo.dos.santos@xxxxxxxxxxx> wrote:
I’ve checked with my managers, and I’m being told that we do have plans to move to Java 11 by next summer (July timeframe). Wikitext is one of key drivers for this transition.

I really would like to avoid diverging release branches if we can; the build system has been the most difficult piece of the project to maintain over the last 2 years, and I don’t look forward to creating a divergent release branch for ~6 months development. For now I’d like to propose we continue with security and build updates, and roadmap towards full Java 11 support for next summer. 

In the short term, I would like to put out a bug fix/security update with Aleksandar’s Guava improvements and a JSoup security update before end of October. Does this sound reasonable to all?

Cheers,
Leo


On Oct 5, 2021, at 8:13 AM, Aleksandar Kurtakov <akurtako@xxxxxxxxxx> wrote:



On Tue, Oct 5, 2021 at 5:55 PM Leo Dos Santos <leo.dos.santos@xxxxxxxxxxx> wrote:
Tasktop is still on Java 8 for various reasons, and our adoption of Java 11 has been delayed. Unfortunately I haven’t been able to get an ETA for when that might change.

Would the group be open to a separate branch / new version (Docs 3.2?) for full Java 11 support or is that still seen as too much to maintain?

What about creating a branch from wikitext.core-3.0.39 for 3.0 maintenance for your needs and have master full steam on Java 11?
 

- Leo


On Oct 5, 2021, at 7:23 AM, Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx> wrote:


On Oct 5, 2021, at 15:37, Aleksandar Kurtakov <akurtako@xxxxxxxxxx> wrote:
I would recommend processing with updating to Java 11. There is a huge cost saving benefit when reducing dependencies.

So may I ask for conclusion on the topic here ? The way I read it right now is until PL agrees non-eclipse plugin parts stay on Java 8 but I hope for a change :)
 

As a member of Mylyn PMC I fully support dropping Java 8 support. It's really difficult to justify staying on Java 8. Frankly, there wasn't a single adopter replying here with a convincing reason to stay on Java 8.


Also, as per https://www.eclipse.org/lists/mylyn-docs-dev/msg00507.html you also volunteered to become PL. I still support that and I'm ready to nominate you as PL.

-Gunnar



_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-docs-dev

--
Leo Dos Santos
Senior Software Engineer, Tasktop Integrations

_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-docs-dev


-- 
Aleksandar Kurtakov
Red Hat Eclipse Team
_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-docs-dev

--
Leo Dos Santos
Senior Software Engineer, Tasktop Integrations

_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-docs-dev


--
Aleksandar Kurtakov
Red Hat Eclipse Team
_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/mylyn-docs-dev

--
Leo Dos Santos
Senior Software Engineer, Tasktop Integrations

Back to the top