Saravanan - As important as this project seems to be to your customer, and how important it is for them not to upgrade, and how valuable is the time of the Tika developers (many or most of whom contribute their time to the project in their own spare time), perhaps *you or your client* should pay the cost of keeping the old version breathing.
You and your client are asking to receive a lot -- what are you offering in return? I am not working on Tika anymore but have huge respect for those who are. Do you and your client share that respect? Why ask the developers to invest *even more* of their time than they already have, for the sake of a client who chooses not to upgrade? Perhaps you or your client would like to pay for the developers' time to do this? You might find someone qualified and available (not me). - Keith On Thu, Jan 22, 2026 at 4:22 PM Saravanan Balakrishnan < [email protected]> wrote: > Thanks for the mail. Is it possible to reconsider for addressing the CVEs > fix alone for the older releases. It would be great for us to keep it up to > date at least for CVEs fix, not official build, SNAPSHOT would also be > greatly appreciated. Kindly revert back. > > Regards, > Saravanan B > > > ----- Original message ----- > From: "Tilman Hausherr" <[email protected]> > To: [email protected] > Subject: Re: Tika older version retention/fix time frame > Date: Thu, Jan 22, 2026 1:06 PM > > > - [CAUTION: This email is from outside the organization. Unless you > trust the sender, don't click links or open attachments as it may be a > phishing email, which can steal your information and compromise your > computer.] > > > > Hi, > > Obviously, NO. > > See also the bold text here: > https://apache.org/legal/release-policy#publication > > I've occasionally done updates because of testing PDFBox 2.0.X. If you > want to release old versions, fork the project. > > Tilman > > Am 22.01.2026 um 05:19 schrieb Saravanan Balakrishnan: > > Hi Tika Team, > Is there a plan to keep it alive and keep it updated with the > vulnerability fix or critical fixes to keep this branch up to date. > Is there any possibility to have a monthly or periodically build the 2.9.5 > build or on demand build and its retention time frame. > Are changes still being submitted to that stream/version/build. > > We understand that it's already in the end of life, there is an issue to > keep the older versions to support our customer. Kindly provide your plan > on the 2.9.5 stream to keep it alive for critical fixes. > > Thanks in advance. > > Regards, > Saravanan B > > > > >
