I've been waiting for some committer consensus on this. I agree with 2.0.0
.

On Mon, Sep 16, 2024 at 4:10 AM Andreas Veithen-Knowles <
andreas.veit...@gmail.com> wrote:

> Note that we need to decide what the version number for the next release
> should be. The switch to the Jakarta APIs is a breaking change, so it can't
> be 1.8.3. If we follow https://semver.org/, then it should actually be
> 2.0.0.
>
> Andreas
>
> On Fri, Sep 13, 2024 at 2:10 PM robertlazarski <robertlazar...@gmail.com>
> wrote:
>
>> An Axis2 1.8.3 release is just weeks away at this point.
>>
>> The delay is explained by the transition from the javax to jakarta
>> namespace and that required changes to nearly every file that we
>> distribute. This includes many dependency updates that also support
>> jakarta.
>>
>> The 1.8.3 release will support the latest Java standards EE10 and Servlet
>> 6.0.
>>
>> On Thu, Sep 12, 2024 at 9:24 PM Ponoran, Elisa-Adela
>> <elisa.ponoran@cpp.canon.invalid> wrote:
>>
>>> Hello,
>>>
>>> Can you please let me know if Axis2 is end-of-life or is it still
>>> maintained?
>>> I see last version of Axis2 *1.8.2,* released in 2022.
>>>
>>> Regards,
>>> Elisa
>>>
>>>
>>>
>>>
>>>
>>> With kind regards,
>>>
>>>
>>>
>>> *Elisa Ponoran*
>>>
>>> Software engineer | System development 31
>>>
>>> +40 743 514 325
>>>
>>> elisa.ponoran@cpp.canon
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> <https://www.cpp.canon/>
>>> Canon Production Printing Romania S.R.L.
>>> ISHO Offices
>>> Bd. Take Ionescu 50-52,
>>> Cladirea B, etaj 5, camera 5.2.
>>> 300124 - Timisoara
>>> Romania | Trade register: RO17191681
>>> www.cpp.canon
>>>
>>>
>>> This message and attachment(s) are intended solely for use by the
>>> addressee and may contain information that is privileged, confidential or
>>> otherwise exempt from disclosure under applicable law. If you are not the
>>> intended recipient or agent thereof responsible for delivering this message
>>> to the intended recipient, you are hereby notified that any dissemination,
>>> distribution or copying of this communication is strictly prohibited. If
>>> you have received this communication in error, please notify the sender
>>> immediately by telephone or with a 'reply' message and delete the message
>>> and its attachment(s), if any, from your system(s). Thank you for your
>>> co-operation.
>>>
>>

Reply via email to