Understood, but our need to upgrade to Java 21 and tomcat 10.X trumped the 
“production“ tag.

> On May 17, 2024, at 11:11 AM, Houser,Leah <hou...@oclc.org> wrote:
> 
> Would love to use it but my company will not accept a pre-release version to 
> run a production application. I really appreciate the work being done here, 
> don't get me wrong.  
> 
> -----Original Message-----
> From: Burton Rhodes <burtonrho...@gmail.com>
> Sent: Friday, May 17, 2024 12:07 PM
> To: Struts Developers List <dev@struts.apache.org>
> Subject: [EXTERNAL] Re: Struts2 7.x official release
> 
> [You don't often get email from burtonrho...@gmail.com. Learn why this is 
> important at https://aka.ms/LearnAboutSenderIdentification ]
> 
> To add to Greg‘s comment, we are using M6 and production without issue. Your 
> mileage may vary though.
> 
> 
>> On May 17, 2024, at 11:00 AM, Greg Huber <gregh3...@gmail.com> wrote:
>> 
>> I am not sure there is a date,  but M6 is quite good and stable.
>> 
>>>> On 17/05/2024 10:55, Sai Charan Teja Pratti wrote:
>>> Hi,
>>> 
>>> Inorder to upgrade to tomcat 10.x, we have dependency with struts2
>>> 7.x Can you please let us know when can we expect the struts2 7.x
>>> official release
>>> 
>>> Thanks,
>>> Sai
>>> 
>>>> On Tue, May 14, 2024 at 2:18 PM Sai Charan Teja Pratti 
>>>> <sai-charan-teja.pra...@broadcom.com> wrote:
>>> 
>>>   Hi,
>>> 
>>>   Inorder to upgrade to tomcat 10.x, we have dependency with struts2 7.x
>>>   When can we expect the struts2 7.x official release
>>> 
>>>   Thanks,
>>>   Sai
>>> 
>>> 
>>> This electronic communication and the information and any files transmitted 
>>> with it, or attached to it, are confidential and are intended solely for 
>>> the use of the individual or entity to whom it is addressed and may contain 
>>> information that is confidential, legally privileged, protected by privacy 
>>> laws, or otherwise restricted from disclosure to anyone else. If you are 
>>> not the intended recipient or the person responsible for delivering the 
>>> e-mail to the intended recipient, you are hereby notified that any use, 
>>> copying, distributing, dissemination, forwarding, printing, or copying of 
>>> this e-mail is strictly prohibited. If you received this e-mail in error, 
>>> please return the e-mail to the sender, delete it from your computer, and 
>>> destroy any printed copy of it.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional 
> commands, e-mail: dev-h...@struts.apache.org
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
> For additional commands, e-mail: dev-h...@struts.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org

Reply via email to