You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@shiro.apache.org by le...@flowlogix.com on 2026/03/31 00:09:22 UTC
Next release of 3.x?
GitHub user lprimak created a discussion: Next 3.x release discussion
Apache Shiro team released 3.0.0-alpha-1 about a month ago.
If you have tried it, can you please share any feedback. Positive or negative.
Thank you
What would you like to see as the next 3.x release?
3.0.0-alpha-2
3.0.0-beta-1
3.0.0-rc-1
3.0.0 (Final)
Re: Feedback urgently needed - Re: Next release of 3.x?
Posted by Lenny Primak <le...@flowlogix.com>.
Understood. Thank you Andreas.
> On Apr 13, 2026, at 2:58 AM, Andreas Reichel <andreas@manticore-
> projects.com> wrote:
>
>
>
>
> Lenny,
>
>
>
>
> thank you for the explanations, I do understand all of this and where it
> comes from.
>
> I only wanted to bring up the idea, that exactly this orthodox approach may
> not help with a faster adoption of Shiro 3.
>
>
>
>
> And no, we have not tested it yet since we do only DB/AD/Text realms in
> plain Java. Sorry.
>
>
>
>
> Best and cheers
>
> Andreas
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Fri, 2026-04-10 at 18:08 -0500, lenny@flowlogix.com wrote:
>
>> Thank you for your feedback, Andreas.
>>
>>
>
>>
>> Shiro has a long-standing constraints about releases:
>>
>> \- Apache projects at least 3 PMV votes for a release
>>
>> \- Shiro follows (and and enforce) strict Semver-compliant releases.
>>
>>
>
>>
>> What that means in practice is that once a major version is released, any
minor version needs to be
>>
>> both API and binary compatible with the major version. We don’t want to
release a major version too early,
>>
>> since if the API changes, we may need to bump the major version again.
>>
>>
>
>>
>> For 3.x, we bumped the base JDK to 17, Jakarta EE to 11 (although 9/10 are
still compatible) and SpringBoot to 4.x
>>
>>
>
>>
>> Have you tried 3.0.0-alpha-1 yet?
>>
>>
>
>>
>>> On Apr 10, 2026, at 3:33 AM, Andreas Reichel <andreas@manticore-
projects.com> wrote:
>>>
>>>
>
>>>
>>> Greetings Lenny and Team,
>>>
>>>
>
>>>
>>> thank you so much for all your work and effort.
>>>
>>> To us, Shiro is one of the great Whisps working endlessly in the
background w/o ever been seen or acknowledged gratefully.
>>>
>>>
>
>>>
>>> From my very personal opinion, I recommend just to release more often (w/o
much voting) by increasing the minor version. We at [manticore-
projects.com](http://manticore-projects.com/) take the latest minor version
anyway and update the major versions only based on CVEs and or JDK
requirements. Only when an issue was found we would roll back to the latest
known working minor version.
>>>
>>>
>
>>>
>>> In short: throw it into the cold water and let see if it swims. A 3.0 out,
followed by fast 3.0.1 and 3.0.2 will work wonders. Blame me for any issues
caused 😄
>>>
>>>
>
>>>
>>> Best and cheers
>>>
>>> Andreas
>>>
>>>
>
>>>
>>>
>
>>>
>>>
>
>>>
>>> On Thu, 2026-04-09 at 15:45 -0500, lenny@flowlogix.com wrote:
>>>
>>>> I have been using 3.0.0-alpha-1 in production for a few weeks now, and
already found an API issue that was fixed in the 3.x branch..
>>>>
>>>> Would love some additional feedback from other users.
>>>>
>>>>
>
>>>>
>>>>> On Apr 9, 2026, at 3:43 PM, lenny@flowlogix.com wrote:
>>>>>
>>>>>
>
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>
>>>>>
>>>>> We really need feedback for Apache Shiro 3.0.0-alpha-1.
>>>>>
>>>>> Can you try it? Any issues uncovered would be really appreciated.
>>>>>
>>>>> Also, can we get some feedback on what to do with our next release, as
seen below?
>>>>>
>>>>>
>
>>>>>
>>>>> We really appreciate the time and effort.
>>>>>
>>>>>
>
>>>>>
>>>>>> On Mar 30, 2026, at 7:09 PM, lenny@flowlogix.com wrote:
>>>>>>
>>>>>>
>
>>>>>>
>>>>>> GitHub user lprimak created a discussion: Next 3.x release discussion
>
> Apache Shiro team released 3.0.0-alpha-1 about a month ago.
> If you have tried it, can you please share any feedback. Positive or
> negative.
>
> Thank you
>>>>>>
>>>>>>
>
>>>>>>
>>>>>> What would you like to see as the next 3.x release?
>>>>>>
>>>>>> 3.0.0-alpha-2
>>>>>>
>>>>>> 3.0.0-beta-1
>>>>>>
>>>>>> 3.0.0-rc-1
>>>>>>
>>>>>> 3.0.0 (Final)
>>
>>
>
>
>
>
Re: Feedback urgently needed - Re: Next release of 3.x?
Posted by Andreas Reichel <an...@manticore-projects.com>.
Lenny,
thank you for the explanations, I do understand all of this and where
it comes from.
I only wanted to bring up the idea, that exactly this orthodox approach
may not help with a faster adoption of Shiro 3.
And no, we have not tested it yet since we do only DB/AD/Text realms in
plain Java. Sorry.
Best and cheers
Andreas
On Fri, 2026-04-10 at 18:08 -0500, lenny@flowlogix.com wrote:
> Thank you for your feedback, Andreas.
>
> Shiro has a long-standing constraints about releases:
> - Apache projects at least 3 PMV votes for a release
> - Shiro follows (and and enforce) strict Semver-compliant releases.
>
> What that means in practice is that once a major version is released,
> any minor version needs to be
> both API and binary compatible with the major version. We don’t want
> to release a major version too early,
> since if the API changes, we may need to bump the major version
> again.
>
> For 3.x, we bumped the base JDK to 17, Jakarta EE to 11 (although
> 9/10 are still compatible) and SpringBoot to 4.x
>
> Have you tried 3.0.0-alpha-1 yet?
>
> > On Apr 10, 2026, at 3:33 AM, Andreas Reichel <andreas@manticore-
> > projects.com> wrote:
> >
> >
> > Greetings Lenny and Team,
> >
> > thank you so much for all your work and effort.
> > To us, Shiro is one of the great Whisps working endlessly in the
> > background w/o ever been seen or acknowledged gratefully.
> >
> > From my very personal opinion, I recommend just to release more
> > often (w/o much voting) by increasing the minor version. We
> > at manticore-projects.com take the latest minor version anyway and
> > update the major versions only based on CVEs and or JDK
> > requirements. Only when an issue was found we would roll back to
> > the latest known working minor version.
> >
> > In short: throw it into the cold water and let see if it swims. A
> > 3.0 out, followed by fast 3.0.1 and 3.0.2 will work wonders. Blame
> > me for any issues caused 😄
> >
> > Best and cheers
> > Andreas
> >
> >
> >
> > On Thu, 2026-04-09 at 15:45 -0500, lenny@flowlogix.com wrote:
> > > I have been using 3.0.0-alpha-1 in production for a few weeks
> > > now, and already found an API issue that was fixed in the 3.x
> > > branch..
> > > Would love some additional feedback from other users.
> > >
> > > > On Apr 9, 2026, at 3:43 PM, lenny@flowlogix.com wrote:
> > > >
> > > > Hi,
> > > >
> > > > We really need feedback for Apache Shiro 3.0.0-alpha-1.
> > > > Can you try it? Any issues uncovered would be really
> > > > appreciated.
> > > > Also, can we get some feedback on what to do with our next
> > > > release, as seen below?
> > > >
> > > > We really appreciate the time and effort.
> > > >
> > > > > On Mar 30, 2026, at 7:09 PM, lenny@flowlogix.com wrote:
> > > > >
> > > > > GitHub user lprimak created a discussion: Next 3.x release
> > > > > discussion
> > > > >
> > > > > Apache Shiro team released 3.0.0-alpha-1 about a month ago.
> > > > > If you have tried it, can you please share any feedback.
> > > > > Positive or negative.
> > > > >
> > > > > Thank you
> > > > >
> > > > > What would you like to see as the next 3.x release?
> > > > >
> > > > > 3.0.0-alpha-2
> > > > >
> > > > > 3.0.0-beta-1
> > > > >
> > > > > 3.0.0-rc-1
> > > > >
> > > > > 3.0.0 (Final)
>
Re: Feedback urgently needed - Re: Next release of 3.x?
Posted by le...@flowlogix.com.
Thank you for your feedback, Andreas.
Shiro has a long-standing constraints about releases:
- Apache projects at least 3 PMV votes for a release
- Shiro follows (and and enforce) strict Semver-compliant releases.
What that means in practice is that once a major version is released, any minor version needs to be
both API and binary compatible with the major version. We don’t want to release a major version too early,
since if the API changes, we may need to bump the major version again.
For 3.x, we bumped the base JDK to 17, Jakarta EE to 11 (although 9/10 are still compatible) and SpringBoot to 4.x
Have you tried 3.0.0-alpha-1 yet?
> On Apr 10, 2026, at 3:33 AM, Andreas Reichel <an...@manticore-projects.com> wrote:
>
> Greetings Lenny and Team,
>
> thank you so much for all your work and effort.
> To us, Shiro is one of the great Whisps working endlessly in the background w/o ever been seen or acknowledged gratefully.
>
> From my very personal opinion, I recommend just to release more often (w/o much voting) by increasing the minor version. We at manticore-projects.com <http://manticore-projects.com/> take the latest minor version anyway and update the major versions only based on CVEs and or JDK requirements. Only when an issue was found we would roll back to the latest known working minor version.
>
> In short: throw it into the cold water and let see if it swims. A 3.0 out, followed by fast 3.0.1 and 3.0.2 will work wonders. Blame me for any issues caused 😄
>
> Best and cheers
> Andreas
>
>
>
> On Thu, 2026-04-09 at 15:45 -0500, lenny@flowlogix.com wrote:
>> I have been using 3.0.0-alpha-1 in production for a few weeks now, and already found an API issue that was fixed in the 3.x branch..
>> Would love some additional feedback from other users.
>>
>>> On Apr 9, 2026, at 3:43 PM, lenny@flowlogix.com wrote:
>>>
>>> Hi,
>>>
>>> We really need feedback for Apache Shiro 3.0.0-alpha-1.
>>> Can you try it? Any issues uncovered would be really appreciated.
>>> Also, can we get some feedback on what to do with our next release, as seen below?
>>>
>>> We really appreciate the time and effort.
>>>
>>>> On Mar 30, 2026, at 7:09 PM, lenny@flowlogix.com wrote:
>>>>
>>>> GitHub user lprimak created a discussion: Next 3.x release discussion
>>>>
>>>> Apache Shiro team released 3.0.0-alpha-1 about a month ago.
>>>> If you have tried it, can you please share any feedback. Positive or negative.
>>>>
>>>> Thank you
>>>>
>>>> What would you like to see as the next 3.x release?
>>>> 3.0.0-alpha-2
>>>> 3.0.0-beta-1
>>>> 3.0.0-rc-1
>>>> 3.0.0 (Final)
Re: Feedback urgently needed - Re: Next release of 3.x?
Posted by Andreas Reichel <an...@manticore-projects.com>.
Greetings Lenny and Team,
thank you so much for all your work and effort.
To us, Shiro is one of the great Whisps working endlessly in the
background w/o ever been seen or acknowledged gratefully.
From my very personal opinion, I recommend just to release more often
(w/o much voting) by increasing the minor version. We at manticore-
projects.com take the latest minor version anyway and update the major
versions only based on CVEs and or JDK requirements. Only when an issue
was found we would roll back to the latest known working minor version.
In short: throw it into the cold water and let see if it swims. A 3.0
out, followed by fast 3.0.1 and 3.0.2 will work wonders. Blame me for
any issues caused 😄
Best and cheers
Andreas
On Thu, 2026-04-09 at 15:45 -0500, lenny@flowlogix.com wrote:
> I have been using 3.0.0-alpha-1 in production for a few weeks now,
> and already found an API issue that was fixed in the 3.x branch..
> Would love some additional feedback from other users.
>
> > On Apr 9, 2026, at 3:43 PM, lenny@flowlogix.com wrote:
> >
> >
> > Hi,
> >
> > We really need feedback for Apache Shiro 3.0.0-alpha-1.
> > Can you try it? Any issues uncovered would be really appreciated.
> > Also, can we get some feedback on what to do with our next release,
> > as seen below?
> >
> > We really appreciate the time and effort.
> >
> > > On Mar 30, 2026, at 7:09 PM, lenny@flowlogix.com wrote:
> > >
> > >
> > > GitHub user lprimak created a discussion: Next 3.x release
> > > discussion
> > >
> > > Apache Shiro team released 3.0.0-alpha-1 about a month ago.
> > > If you have tried it, can you please share any feedback. Positive
> > > or negative.
> > >
> > > Thank you
> > >
> > > What would you like to see as the next 3.x release?
> > >
> > > 3.0.0-alpha-2
> > >
> > > 3.0.0-beta-1
> > >
> > > 3.0.0-rc-1
> > >
> > > 3.0.0 (Final)
> >
>
Re: Feedback urgently needed - Re: Next release of 3.x?
Posted by le...@flowlogix.com.
I have been using 3.0.0-alpha-1 in production for a few weeks now, and already found an API issue that was fixed in the 3.x branch..
Would love some additional feedback from other users.
> On Apr 9, 2026, at 3:43 PM, lenny@flowlogix.com wrote:
>
> Hi,
>
> We really need feedback for Apache Shiro 3.0.0-alpha-1.
> Can you try it? Any issues uncovered would be really appreciated.
> Also, can we get some feedback on what to do with our next release, as seen below?
>
> We really appreciate the time and effort.
>
>> On Mar 30, 2026, at 7:09 PM, lenny@flowlogix.com wrote:
>>
>> GitHub user lprimak created a discussion: Next 3.x release discussion
>>
>> Apache Shiro team released 3.0.0-alpha-1 about a month ago.
>> If you have tried it, can you please share any feedback. Positive or negative.
>>
>> Thank you
>>
>> What would you like to see as the next 3.x release?
>> 3.0.0-alpha-2
>> 3.0.0-beta-1
>> 3.0.0-rc-1
>> 3.0.0 (Final)
>
Feedback urgently needed - Re: Next release of 3.x?
Posted by le...@flowlogix.com.
Hi,
We really need feedback for Apache Shiro 3.0.0-alpha-1.
Can you try it? Any issues uncovered would be really appreciated.
Also, can we get some feedback on what to do with our next release, as seen below?
We really appreciate the time and effort.
> On Mar 30, 2026, at 7:09 PM, lenny@flowlogix.com wrote:
>
> GitHub user lprimak created a discussion: Next 3.x release discussion
>
> Apache Shiro team released 3.0.0-alpha-1 about a month ago.
> If you have tried it, can you please share any feedback. Positive or negative.
>
> Thank you
>
> What would you like to see as the next 3.x release?
> 3.0.0-alpha-2
> 3.0.0-beta-1
> 3.0.0-rc-1
> 3.0.0 (Final)