You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by Tim Allison <ta...@apache.org> on 2023/09/12 14:49:31 UTC
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
>If Tika users will be happy to move on and drop Java 8 and/or javax.
Please drop them :)))
Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x and
dropping support for Java 8 and javax in September 2024?
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by David Pilato <da...@pilato.fr>.
The sooner, the better IMHO.
+1 to drop Java8 support.
David
--
David Pilato, elastic.co
Developer | Evangelist,
Le 12 sept. 2023 à 16:50 +0200, Tim Allison <ta...@apache.org>, a écrit :
> >If Tika users will be happy to move on and drop Java 8 and/or javax. Please drop them :)))
>
> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x and dropping support for Java 8 and javax in September 2024?
>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Timo Boehme <ti...@ontochem.com>.
+1
Our company did the switch to Java 11 during this year. Thus fine from
my side.
Thanks,
Timo
Am 12.09.23 um 16:56 schrieb Tim Allison:
> Sorry, let me try that again.
>
> The proposal:
> 1) start parallel main (3.x) and branch_2x branches now.
> 2) cut a first release of 3.0.0 by the end of September (maybe October) of
> 2023
> 3) Set the EOL for the 2.x branch one year after the first release of 3.0.0
> -- possibly set 2.x to "security fixes only" 6 months after the first
> release of 3.0.0?
>
> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
> major changes.
>
> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org> wrote:
>
>>> If Tika users will be happy to move on and drop Java 8 and/or javax.
>> Please drop them :)))
>>
>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
>> and dropping support for Java 8 and javax in September 2024?
>>
>>
>
--
OntoChem GmbH
Blücherstraße 24
06120 Halle (Saale)
Germany
email: timo.boehme@ontochem.com | web: www.ontochem.com
HRB 215461 Amtsgericht Stendal | USt-IdNr.: DE246232735
managing directors: Dr. Lutz Weber (CEO), Dr. Felix Berthelmann (COO)
Re: [External] Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Tim Allison <ta...@apache.org>.
Y, totally get it.
How about shortening the EOL of Tika 2.x (and Java 8) to 6 months after the
Tika 3.x/Java 11 release?
On Thu, Sep 14, 2023 at 5:41 AM Sandeep Kulkarni
<Sa...@veritas.com.invalid> wrote:
> As a long time user of Tika, I would like to suggest Java 11 should be
> supported for 3.x. Java 17 is still quite new for Enterprise customers.
> They have just now started migrating slowly to Java 11.
>
> Regards,
> Sandeep Kulkarni
>
>
Re: [External] Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Tim Allison <ta...@apache.org>.
Y, totally get it.
How about shortening the EOL of Tika 2.x (and Java 8) to 6 months after the
Tika 3.x/Java 11 release?
On Thu, Sep 14, 2023 at 5:41 AM Sandeep Kulkarni
<Sa...@veritas.com.invalid> wrote:
> As a long time user of Tika, I would like to suggest Java 11 should be
> supported for 3.x. Java 17 is still quite new for Enterprise customers.
> They have just now started migrating slowly to Java 11.
>
> Regards,
> Sandeep Kulkarni
>
>
RE: [External] Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Sandeep Kulkarni <Sa...@veritas.com.INVALID>.
As a long time user of Tika, I would like to suggest Java 11 should be supported for 3.x. Java 17 is still quite new for Enterprise customers. They have just now started migrating slowly to Java 11.
Regards,
Sandeep Kulkarni
From: David Pilato <da...@pilato.fr>
Sent: Thursday, September 14, 2023 2:14 PM
To: user@tika.apache.org
Cc: dev@tika.apache.org
Subject: [External] Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you believe this is a phishing email, use the Report to Cybersecurity icon in Outlook.
I'm all for Java17 on 3.x. (A)
David Pilato
david@pilato.fr<ma...@pilato.fr>
06 13 03 08 41
Le 13 sept. 2023 à 21:26 +0200, Tim Allison <ta...@apache.org>>, a écrit :
We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one more year. I've started the branches and started making some changes in this direction.
Is it worth pushing this modernization further or faster, with either:
a) Jump to Java 17 now and keep Java 8 in 2.x for one more year
b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say 6 months or fewer?
Thank you, all, for your feedback!
Best,
Tim
RE: [External] Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Sandeep Kulkarni via user <us...@tika.apache.org>.
As a long time user of Tika, I would like to suggest Java 11 should be supported for 3.x. Java 17 is still quite new for Enterprise customers. They have just now started migrating slowly to Java 11.
Regards,
Sandeep Kulkarni
From: David Pilato <da...@pilato.fr>
Sent: Thursday, September 14, 2023 2:14 PM
To: user@tika.apache.org
Cc: dev@tika.apache.org
Subject: [External] Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you believe this is a phishing email, use the Report to Cybersecurity icon in Outlook.
I'm all for Java17 on 3.x. (A)
David Pilato
david@pilato.fr<ma...@pilato.fr>
06 13 03 08 41
Le 13 sept. 2023 à 21:26 +0200, Tim Allison <ta...@apache.org>>, a écrit :
We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one more year. I've started the branches and started making some changes in this direction.
Is it worth pushing this modernization further or faster, with either:
a) Jump to Java 17 now and keep Java 8 in 2.x for one more year
b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say 6 months or fewer?
Thank you, all, for your feedback!
Best,
Tim
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by David Pilato <da...@pilato.fr>.
I'm all for Java17 on 3.x. (A)
David Pilato
david@pilato.fr
06 13 03 08 41
Le 13 sept. 2023 à 21:26 +0200, Tim Allison <ta...@apache.org>, a écrit :
> We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one more year. I've started the branches and started making some changes in this direction.
>
> Is it worth pushing this modernization further or faster, with either:
> a) Jump to Java 17 now and keep Java 8 in 2.x for one more year
> b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say 6 months or fewer?
>
> Thank you, all, for your feedback!
>
> Best,
>
> Tim
>
> >
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Ken Krugler <kk...@transpac.com>.
Hi Tim,
I think jumping to Java 17 would be a bit much for 3.x.
I would vote for a shorter EOL for Tika 2.x
What I’ve seen is that users who are forced to continue using older versions of Java are generally able to back port changes they need, once support is EOL. So if there’s a critical bug fix in 3.x in 9 months, anyone still on Java 8 would be able to fork/fix it themselves, without relying on the (small, over-loaded) Tika community to keep Java 8 actively supported.
— Ken
> On Sep 13, 2023, at 12:26 PM, Tim Allison <ta...@apache.org> wrote:
>
> We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one more year. I've started the branches and started making some changes in this direction.
>
> Is it worth pushing this modernization further or faster, with either:
> a) Jump to Java 17 now and keep Java 8 in 2.x for one more year
> b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say 6 months or fewer?
>
> Thank you, all, for your feedback!
>
> Best,
>
> Tim
>
>
--------------------------
Ken Krugler
http://www.scaleunlimited.com
Custom big data solutions
Flink, Pinot, Solr, Elasticsearch
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Ken Krugler <kk...@transpac.com>.
Hi Tim,
I think jumping to Java 17 would be a bit much for 3.x.
I would vote for a shorter EOL for Tika 2.x
What I’ve seen is that users who are forced to continue using older versions of Java are generally able to back port changes they need, once support is EOL. So if there’s a critical bug fix in 3.x in 9 months, anyone still on Java 8 would be able to fork/fix it themselves, without relying on the (small, over-loaded) Tika community to keep Java 8 actively supported.
— Ken
> On Sep 13, 2023, at 12:26 PM, Tim Allison <ta...@apache.org> wrote:
>
> We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one more year. I've started the branches and started making some changes in this direction.
>
> Is it worth pushing this modernization further or faster, with either:
> a) Jump to Java 17 now and keep Java 8 in 2.x for one more year
> b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say 6 months or fewer?
>
> Thank you, all, for your feedback!
>
> Best,
>
> Tim
>
>
--------------------------
Ken Krugler
http://www.scaleunlimited.com
Custom big data solutions
Flink, Pinot, Solr, Elasticsearch
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by David Pilato <da...@pilato.fr>.
I'm all for Java17 on 3.x. (A)
David Pilato
david@pilato.fr
06 13 03 08 41
Le 13 sept. 2023 à 21:26 +0200, Tim Allison <ta...@apache.org>, a écrit :
> We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for one more year. I've started the branches and started making some changes in this direction.
>
> Is it worth pushing this modernization further or faster, with either:
> a) Jump to Java 17 now and keep Java 8 in 2.x for one more year
> b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in say 6 months or fewer?
>
> Thank you, all, for your feedback!
>
> Best,
>
> Tim
>
> >
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Tim Allison <ta...@apache.org>.
We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for
one more year. I've started the branches and started making some changes
in this direction.
Is it worth pushing this modernization further or faster, with either:
a) Jump to Java 17 now and keep Java 8 in 2.x for one more year
b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in
say 6 months or fewer?
Thank you, all, for your feedback!
Best,
Tim
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Tim Allison <ta...@apache.org>.
We seem to have consensus on Java 11 for 3.x and keep Java 8 for 2.x for
one more year. I've started the branches and started making some changes
in this direction.
Is it worth pushing this modernization further or faster, with either:
a) Jump to Java 17 now and keep Java 8 in 2.x for one more year
b) Keep Java 11 in "main"/3.x now and set the EOL for Tika 2.x/Java 8 in
say 6 months or fewer?
Thank you, all, for your feedback!
Best,
Tim
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Tim Allison <ta...@apache.org>.
Let's move forth!
dual branches for now: main and branch_2x
https://issues.apache.org/jira/browse/TIKA-4127
On Wed, Sep 13, 2023 at 9:03 AM Maxim Solodovnik <so...@gmail.com>
wrote:
> Hello,
>
> from mobile (sorry for typos ;)
>
>
> On Wed, Sep 13, 2023, 11:28 Adam Rauch <ad...@labkey.com> wrote:
>
>> +1 on requiring Java 11... no problem there.
>>
>> Can you clarify what exactly "require jakarta" means? Tika will link to
>> dependencies that happen use jakarta package names, but will have no
>> problem running in a javax container (such as Tomcat 9.0.x) with javax
>> libraries present? Or something else?
>>
>
> As per my understanding Tika depends on CXF+Spring
> Not sure if these two will work with their previous versions that might
> present in webapp .....
>
> Adam
>> On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote:
>>
>> +1 from our side, we moved to java 11 last year.
>>
>> Best,
>> Luis
>>
>>
>> Em ter, 12 de set de 2023 19:01, Ken Krugler <kk...@transpac.com>
>> escreveu:
>>
>>> +1
>>>
>>> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>>>
>>> Sorry, let me try that again.
>>>
>>> The proposal:
>>> 1) start parallel main (3.x) and branch_2x branches now.
>>> 2) cut a first release of 3.0.0 by the end of September (maybe October)
>>> of 2023
>>> 3) Set the EOL for the 2.x branch one year after the first release of
>>> 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first
>>> release of 3.0.0?
>>>
>>> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
>>> major changes.
>>>
>>> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org>
>>> wrote:
>>>
>>>> >If Tika users will be happy to move on and drop Java 8 and/or javax.
>>>> Please drop them :)))
>>>>
>>>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
>>>> and dropping support for Java 8 and javax in September 2024?
>>>>
>>>>
>>> --------------------------
>>> Ken Krugler
>>> http://www.scaleunlimited.com
>>> Custom big data solutions
>>> Flink, Pinot, Solr, Elasticsearch
>>>
>>>
>>>
>>>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Tim Allison <ta...@apache.org>.
Let's move forth!
dual branches for now: main and branch_2x
https://issues.apache.org/jira/browse/TIKA-4127
On Wed, Sep 13, 2023 at 9:03 AM Maxim Solodovnik <so...@gmail.com>
wrote:
> Hello,
>
> from mobile (sorry for typos ;)
>
>
> On Wed, Sep 13, 2023, 11:28 Adam Rauch <ad...@labkey.com> wrote:
>
>> +1 on requiring Java 11... no problem there.
>>
>> Can you clarify what exactly "require jakarta" means? Tika will link to
>> dependencies that happen use jakarta package names, but will have no
>> problem running in a javax container (such as Tomcat 9.0.x) with javax
>> libraries present? Or something else?
>>
>
> As per my understanding Tika depends on CXF+Spring
> Not sure if these two will work with their previous versions that might
> present in webapp .....
>
> Adam
>> On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote:
>>
>> +1 from our side, we moved to java 11 last year.
>>
>> Best,
>> Luis
>>
>>
>> Em ter, 12 de set de 2023 19:01, Ken Krugler <kk...@transpac.com>
>> escreveu:
>>
>>> +1
>>>
>>> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>>>
>>> Sorry, let me try that again.
>>>
>>> The proposal:
>>> 1) start parallel main (3.x) and branch_2x branches now.
>>> 2) cut a first release of 3.0.0 by the end of September (maybe October)
>>> of 2023
>>> 3) Set the EOL for the 2.x branch one year after the first release of
>>> 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first
>>> release of 3.0.0?
>>>
>>> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
>>> major changes.
>>>
>>> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org>
>>> wrote:
>>>
>>>> >If Tika users will be happy to move on and drop Java 8 and/or javax.
>>>> Please drop them :)))
>>>>
>>>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
>>>> and dropping support for Java 8 and javax in September 2024?
>>>>
>>>>
>>> --------------------------
>>> Ken Krugler
>>> http://www.scaleunlimited.com
>>> Custom big data solutions
>>> Flink, Pinot, Solr, Elasticsearch
>>>
>>>
>>>
>>>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello,
from mobile (sorry for typos ;)
On Wed, Sep 13, 2023, 11:28 Adam Rauch <ad...@labkey.com> wrote:
> +1 on requiring Java 11... no problem there.
>
> Can you clarify what exactly "require jakarta" means? Tika will link to
> dependencies that happen use jakarta package names, but will have no
> problem running in a javax container (such as Tomcat 9.0.x) with javax
> libraries present? Or something else?
>
As per my understanding Tika depends on CXF+Spring
Not sure if these two will work with their previous versions that might
present in webapp .....
Adam
> On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote:
>
> +1 from our side, we moved to java 11 last year.
>
> Best,
> Luis
>
>
> Em ter, 12 de set de 2023 19:01, Ken Krugler <kk...@transpac.com>
> escreveu:
>
>> +1
>>
>> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>>
>> Sorry, let me try that again.
>>
>> The proposal:
>> 1) start parallel main (3.x) and branch_2x branches now.
>> 2) cut a first release of 3.0.0 by the end of September (maybe October)
>> of 2023
>> 3) Set the EOL for the 2.x branch one year after the first release of
>> 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first
>> release of 3.0.0?
>>
>> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
>> major changes.
>>
>> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org> wrote:
>>
>>> >If Tika users will be happy to move on and drop Java 8 and/or javax.
>>> Please drop them :)))
>>>
>>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
>>> and dropping support for Java 8 and javax in September 2024?
>>>
>>>
>> --------------------------
>> Ken Krugler
>> http://www.scaleunlimited.com
>> Custom big data solutions
>> Flink, Pinot, Solr, Elasticsearch
>>
>>
>>
>>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello,
from mobile (sorry for typos ;)
On Wed, Sep 13, 2023, 11:28 Adam Rauch <ad...@labkey.com> wrote:
> +1 on requiring Java 11... no problem there.
>
> Can you clarify what exactly "require jakarta" means? Tika will link to
> dependencies that happen use jakarta package names, but will have no
> problem running in a javax container (such as Tomcat 9.0.x) with javax
> libraries present? Or something else?
>
As per my understanding Tika depends on CXF+Spring
Not sure if these two will work with their previous versions that might
present in webapp .....
Adam
> On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote:
>
> +1 from our side, we moved to java 11 last year.
>
> Best,
> Luis
>
>
> Em ter, 12 de set de 2023 19:01, Ken Krugler <kk...@transpac.com>
> escreveu:
>
>> +1
>>
>> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>>
>> Sorry, let me try that again.
>>
>> The proposal:
>> 1) start parallel main (3.x) and branch_2x branches now.
>> 2) cut a first release of 3.0.0 by the end of September (maybe October)
>> of 2023
>> 3) Set the EOL for the 2.x branch one year after the first release of
>> 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first
>> release of 3.0.0?
>>
>> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
>> major changes.
>>
>> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org> wrote:
>>
>>> >If Tika users will be happy to move on and drop Java 8 and/or javax.
>>> Please drop them :)))
>>>
>>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
>>> and dropping support for Java 8 and javax in September 2024?
>>>
>>>
>> --------------------------
>> Ken Krugler
>> http://www.scaleunlimited.com
>> Custom big data solutions
>> Flink, Pinot, Solr, Elasticsearch
>>
>>
>>
>>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Adam Rauch <ad...@labkey.com.INVALID>.
+1 on requiring Java 11... no problem there.
Can you clarify what exactly "require jakarta" means? Tika will link to
dependencies that happen use jakarta package names, but will have no
problem running in a javax container (such as Tomcat 9.0.x) with javax
libraries present? Or something else?
Thanks,
Adam
On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote:
> +1 from our side, we moved to java 11 last year.
>
> Best,
> Luis
>
>
> Em ter, 12 de set de 2023 19:01, Ken Krugler
> <kk...@transpac.com> escreveu:
>
> +1
>
>> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>>
>> Sorry, let me try that again.
>>
>> The proposal:
>> 1) start parallel main (3.x) and branch_2x branches now.
>> 2) cut a first release of 3.0.0 by the end of September (maybe
>> October) of 2023
>> 3) Set the EOL for the 2.x branch one year after the first
>> release of 3.0.0 -- possibly set 2.x to "security fixes only" 6
>> months after the first release of 3.0.0?
>>
>> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many
>> other major changes.
>>
>> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison
>> <ta...@apache.org> wrote:
>>
>> >If Tika users will be happy to move on and drop Java 8
>> and/or javax. Please drop them :)))
>>
>> Fellow devs and broader Tika community, are we ok with
>> EOL'ing Tika 2.x and dropping support for Java 8 and javax in
>> September 2024?
>>
>
> --------------------------
> Ken Krugler
> http://www.scaleunlimited.com
> Custom big data solutions
> Flink, Pinot, Solr, Elasticsearch
>
>
>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Adam Rauch <ad...@labkey.com>.
+1 on requiring Java 11... no problem there.
Can you clarify what exactly "require jakarta" means? Tika will link to
dependencies that happen use jakarta package names, but will have no
problem running in a javax container (such as Tomcat 9.0.x) with javax
libraries present? Or something else?
Thanks,
Adam
On 9/12/2023 9:11 PM, Luís Filipe Nassif wrote:
> +1 from our side, we moved to java 11 last year.
>
> Best,
> Luis
>
>
> Em ter, 12 de set de 2023 19:01, Ken Krugler
> <kk...@transpac.com> escreveu:
>
> +1
>
>> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>>
>> Sorry, let me try that again.
>>
>> The proposal:
>> 1) start parallel main (3.x) and branch_2x branches now.
>> 2) cut a first release of 3.0.0 by the end of September (maybe
>> October) of 2023
>> 3) Set the EOL for the 2.x branch one year after the first
>> release of 3.0.0 -- possibly set 2.x to "security fixes only" 6
>> months after the first release of 3.0.0?
>>
>> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many
>> other major changes.
>>
>> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison
>> <ta...@apache.org> wrote:
>>
>> >If Tika users will be happy to move on and drop Java 8
>> and/or javax. Please drop them :)))
>>
>> Fellow devs and broader Tika community, are we ok with
>> EOL'ing Tika 2.x and dropping support for Java 8 and javax in
>> September 2024?
>>
>
> --------------------------
> Ken Krugler
> http://www.scaleunlimited.com
> Custom big data solutions
> Flink, Pinot, Solr, Elasticsearch
>
>
>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Luís Filipe Nassif <lf...@gmail.com>.
+1 from our side, we moved to java 11 last year.
Best,
Luis
Em ter, 12 de set de 2023 19:01, Ken Krugler <kk...@transpac.com>
escreveu:
> +1
>
> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>
> Sorry, let me try that again.
>
> The proposal:
> 1) start parallel main (3.x) and branch_2x branches now.
> 2) cut a first release of 3.0.0 by the end of September (maybe October) of
> 2023
> 3) Set the EOL for the 2.x branch one year after the first release of
> 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first
> release of 3.0.0?
>
> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
> major changes.
>
> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org> wrote:
>
>> >If Tika users will be happy to move on and drop Java 8 and/or javax.
>> Please drop them :)))
>>
>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
>> and dropping support for Java 8 and javax in September 2024?
>>
>>
> --------------------------
> Ken Krugler
> http://www.scaleunlimited.com
> Custom big data solutions
> Flink, Pinot, Solr, Elasticsearch
>
>
>
>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Luís Filipe Nassif <lf...@gmail.com>.
+1 from our side, we moved to java 11 last year.
Best,
Luis
Em ter, 12 de set de 2023 19:01, Ken Krugler <kk...@transpac.com>
escreveu:
> +1
>
> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>
> Sorry, let me try that again.
>
> The proposal:
> 1) start parallel main (3.x) and branch_2x branches now.
> 2) cut a first release of 3.0.0 by the end of September (maybe October) of
> 2023
> 3) Set the EOL for the 2.x branch one year after the first release of
> 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first
> release of 3.0.0?
>
> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
> major changes.
>
> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org> wrote:
>
>> >If Tika users will be happy to move on and drop Java 8 and/or javax.
>> Please drop them :)))
>>
>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
>> and dropping support for Java 8 and javax in September 2024?
>>
>>
> --------------------------
> Ken Krugler
> http://www.scaleunlimited.com
> Custom big data solutions
> Flink, Pinot, Solr, Elasticsearch
>
>
>
>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Ken Krugler <kk...@transpac.com>.
+1
> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>
> Sorry, let me try that again.
>
> The proposal:
> 1) start parallel main (3.x) and branch_2x branches now.
> 2) cut a first release of 3.0.0 by the end of September (maybe October) of 2023
> 3) Set the EOL for the 2.x branch one year after the first release of 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first release of 3.0.0?
>
> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other major changes.
>
> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <tallison@apache.org <ma...@apache.org>> wrote:
>> >If Tika users will be happy to move on and drop Java 8 and/or javax. Please drop them :)))
>>
>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x and dropping support for Java 8 and javax in September 2024?
>>
--------------------------
Ken Krugler
http://www.scaleunlimited.com
Custom big data solutions
Flink, Pinot, Solr, Elasticsearch
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Ken Krugler <kk...@transpac.com>.
+1
> On Sep 12, 2023, at 7:56 AM, Tim Allison <ta...@apache.org> wrote:
>
> Sorry, let me try that again.
>
> The proposal:
> 1) start parallel main (3.x) and branch_2x branches now.
> 2) cut a first release of 3.0.0 by the end of September (maybe October) of 2023
> 3) Set the EOL for the 2.x branch one year after the first release of 3.0.0 -- possibly set 2.x to "security fixes only" 6 months after the first release of 3.0.0?
>
> In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other major changes.
>
> On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <tallison@apache.org <ma...@apache.org>> wrote:
>> >If Tika users will be happy to move on and drop Java 8 and/or javax. Please drop them :)))
>>
>> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x and dropping support for Java 8 and javax in September 2024?
>>
--------------------------
Ken Krugler
http://www.scaleunlimited.com
Custom big data solutions
Flink, Pinot, Solr, Elasticsearch
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Tim Allison <ta...@apache.org>.
Sorry, let me try that again.
The proposal:
1) start parallel main (3.x) and branch_2x branches now.
2) cut a first release of 3.0.0 by the end of September (maybe October) of
2023
3) Set the EOL for the 2.x branch one year after the first release of 3.0.0
-- possibly set 2.x to "security fixes only" 6 months after the first
release of 3.0.0?
In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
major changes.
On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org> wrote:
> >If Tika users will be happy to move on and drop Java 8 and/or javax.
> Please drop them :)))
>
> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
> and dropping support for Java 8 and javax in September 2024?
>
>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by David Pilato <da...@pilato.fr>.
The sooner, the better IMHO.
+1 to drop Java8 support.
David
--
David Pilato, elastic.co
Developer | Evangelist,
Le 12 sept. 2023 à 16:50 +0200, Tim Allison <ta...@apache.org>, a écrit :
> >If Tika users will be happy to move on and drop Java 8 and/or javax. Please drop them :)))
>
> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x and dropping support for Java 8 and javax in September 2024?
>
Re: [DISCUSS] Release planning for 3.x and 2.x's EOL
Posted by Tim Allison <ta...@apache.org>.
Sorry, let me try that again.
The proposal:
1) start parallel main (3.x) and branch_2x branches now.
2) cut a first release of 3.0.0 by the end of September (maybe October) of
2023
3) Set the EOL for the 2.x branch one year after the first release of 3.0.0
-- possibly set 2.x to "security fixes only" 6 months after the first
release of 3.0.0?
In 3.x, we'd require Java 11 and jakarta. We wouldn't make many other
major changes.
On Tue, Sep 12, 2023 at 10:49 AM Tim Allison <ta...@apache.org> wrote:
> >If Tika users will be happy to move on and drop Java 8 and/or javax.
> Please drop them :)))
>
> Fellow devs and broader Tika community, are we ok with EOL'ing Tika 2.x
> and dropping support for Java 8 and javax in September 2024?
>
>