You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shiro.apache.org by Les Hazlewood <lh...@apache.org> on 2010/12/06 20:07:18 UTC
Next release
Do you guys wanna try to get out at least a point release to clear out
as many issues as we can before the holidays? I think it'd be a good
idea. Any ideas?
Regards,
Les
Re: Next release
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Ahh, this is a micro release. Duh.
Regards,
Alan
On Dec 11, 2010, at 1:47 PM, Les Hazlewood wrote:
> The release I was suggesting that may go out before the holidays would
> be a bug-fix point release. If we agree to Struts2 and/or Wicket
> being support modules, they would be new features and I would expect
> they go in the 1.2 release.
>
> Also, my personal opinion is that I'm firmly against (as a matter of
> general practice) that we release any new feature without
> documentation. I would expect there would be new site pages under
> https://cwiki.apache.org/confluence/display/SHIRO/Integration
> representing each module and how to use it as well as JavaDoc for
> every public and protected method/member.
>
> Spring, Hibernate, Tomcat, etc. are all successful largely in part
> because of stellar documentation. IMO, we need to live up to these
> standards.
>
> Regards,
>
> Les
>
> On Sat, Dec 11, 2010 at 8:39 AM, Alan D. Cabrera <li...@toolazydogs.com> wrote:
>> I don't see why the struts 2 stuff cannot make it into this release.
>>
>>
>> Regards,
>> Alan
>>
>> On Dec 9, 2010, at 2:27 PM, Les Hazlewood wrote:
>>
>>> There are a few issues that have come in the last week that might
>>> justify a quick point release. I just created a 1.1.x branch to
>>> account for any bugs we might want to fix in a point release (if we
>>> actually do one).
>>>
>>> With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all
>>> forward-incompatible API changes and enhancements can go in there
>>> (unless anyone feels otherwise). We just need to know that if we
>>> apply any patches to the 1.1.x point branch, we should do the same on
>>> the trunk.
>>>
>>> Cheers,
>>>
>>> Les
Re: Next release
Posted by Les Hazlewood <lh...@apache.org>.
The release I was suggesting that may go out before the holidays would
be a bug-fix point release. If we agree to Struts2 and/or Wicket
being support modules, they would be new features and I would expect
they go in the 1.2 release.
Also, my personal opinion is that I'm firmly against (as a matter of
general practice) that we release any new feature without
documentation. I would expect there would be new site pages under
https://cwiki.apache.org/confluence/display/SHIRO/Integration
representing each module and how to use it as well as JavaDoc for
every public and protected method/member.
Spring, Hibernate, Tomcat, etc. are all successful largely in part
because of stellar documentation. IMO, we need to live up to these
standards.
Regards,
Les
On Sat, Dec 11, 2010 at 8:39 AM, Alan D. Cabrera <li...@toolazydogs.com> wrote:
> I don't see why the struts 2 stuff cannot make it into this release.
>
>
> Regards,
> Alan
>
> On Dec 9, 2010, at 2:27 PM, Les Hazlewood wrote:
>
>> There are a few issues that have come in the last week that might
>> justify a quick point release. I just created a 1.1.x branch to
>> account for any bugs we might want to fix in a point release (if we
>> actually do one).
>>
>> With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all
>> forward-incompatible API changes and enhancements can go in there
>> (unless anyone feels otherwise). We just need to know that if we
>> apply any patches to the 1.1.x point branch, we should do the same on
>> the trunk.
>>
>> Cheers,
>>
>> Les
Re: Next release
Posted by Les Hazlewood <lh...@apache.org>.
Cool - thanks for forwarding!
On Tue, Dec 14, 2010 at 9:08 AM, Kalle Korhonen
<ka...@gmail.com> wrote:
> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_launches
>
> Kalle
>
> On Sat, Dec 11, 2010 at 9:06 AM, Alan D. Cabrera <ad...@toolazydogs.com> wrote:
>> A little color to my thinking. I don't see this plugins site being available any time soon. I also see other non-critical support modules in this release as well.
>>
>> I think it's a good idea to place the struts2 support stuff in now and we can release it on its own, with the other support modules, when the plugins site becomes available.
>>
>>
>> Regards,
>> Alan
>>
>> On Dec 11, 2010, at 8:39 AM, Alan D. Cabrera wrote:
>>
>>> I don't see why the struts 2 stuff cannot make it into this release.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>> On Dec 9, 2010, at 2:27 PM, Les Hazlewood wrote:
>>>
>>>> There are a few issues that have come in the last week that might
>>>> justify a quick point release. I just created a 1.1.x branch to
>>>> account for any bugs we might want to fix in a point release (if we
>>>> actually do one).
>>>>
>>>> With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all
>>>> forward-incompatible API changes and enhancements can go in there
>>>> (unless anyone feels otherwise). We just need to know that if we
>>>> apply any patches to the 1.1.x point branch, we should do the same on
>>>> the trunk.
>>>>
>>>> Cheers,
>>>>
>>>> Les
Re: Next release
Posted by Kalle Korhonen <ka...@gmail.com>.
https://blogs.apache.org/foundation/entry/the_apache_software_foundation_launches
Kalle
On Sat, Dec 11, 2010 at 9:06 AM, Alan D. Cabrera <ad...@toolazydogs.com> wrote:
> A little color to my thinking. I don't see this plugins site being available any time soon. I also see other non-critical support modules in this release as well.
>
> I think it's a good idea to place the struts2 support stuff in now and we can release it on its own, with the other support modules, when the plugins site becomes available.
>
>
> Regards,
> Alan
>
> On Dec 11, 2010, at 8:39 AM, Alan D. Cabrera wrote:
>
>> I don't see why the struts 2 stuff cannot make it into this release.
>>
>>
>> Regards,
>> Alan
>>
>> On Dec 9, 2010, at 2:27 PM, Les Hazlewood wrote:
>>
>>> There are a few issues that have come in the last week that might
>>> justify a quick point release. I just created a 1.1.x branch to
>>> account for any bugs we might want to fix in a point release (if we
>>> actually do one).
>>>
>>> With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all
>>> forward-incompatible API changes and enhancements can go in there
>>> (unless anyone feels otherwise). We just need to know that if we
>>> apply any patches to the 1.1.x point branch, we should do the same on
>>> the trunk.
>>>
>>> Cheers,
>>>
>>> Les
>>
>
>
Re: Next release
Posted by Kalle Korhonen <ka...@gmail.com>.
Perhaps. But in any event, the release of support modules don't have
to and probably shouldn't be tied to the release of the core/main
modules.
Kalle
On Sat, Dec 11, 2010 at 9:06 AM, Alan D. Cabrera <ad...@toolazydogs.com> wrote:
> A little color to my thinking. I don't see this plugins site being available any time soon. I also see other non-critical support modules in this release as well.
>
> I think it's a good idea to place the struts2 support stuff in now and we can release it on its own, with the other support modules, when the plugins site becomes available.
>
>
> Regards,
> Alan
>
> On Dec 11, 2010, at 8:39 AM, Alan D. Cabrera wrote:
>
>> I don't see why the struts 2 stuff cannot make it into this release.
>>
>>
>> Regards,
>> Alan
>>
>> On Dec 9, 2010, at 2:27 PM, Les Hazlewood wrote:
>>
>>> There are a few issues that have come in the last week that might
>>> justify a quick point release. I just created a 1.1.x branch to
>>> account for any bugs we might want to fix in a point release (if we
>>> actually do one).
>>>
>>> With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all
>>> forward-incompatible API changes and enhancements can go in there
>>> (unless anyone feels otherwise). We just need to know that if we
>>> apply any patches to the 1.1.x point branch, we should do the same on
>>> the trunk.
>>>
>>> Cheers,
>>>
>>> Les
>>
>
>
Re: Next release
Posted by "Alan D. Cabrera" <ad...@toolazydogs.com>.
A little color to my thinking. I don't see this plugins site being available any time soon. I also see other non-critical support modules in this release as well.
I think it's a good idea to place the struts2 support stuff in now and we can release it on its own, with the other support modules, when the plugins site becomes available.
Regards,
Alan
On Dec 11, 2010, at 8:39 AM, Alan D. Cabrera wrote:
> I don't see why the struts 2 stuff cannot make it into this release.
>
>
> Regards,
> Alan
>
> On Dec 9, 2010, at 2:27 PM, Les Hazlewood wrote:
>
>> There are a few issues that have come in the last week that might
>> justify a quick point release. I just created a 1.1.x branch to
>> account for any bugs we might want to fix in a point release (if we
>> actually do one).
>>
>> With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all
>> forward-incompatible API changes and enhancements can go in there
>> (unless anyone feels otherwise). We just need to know that if we
>> apply any patches to the 1.1.x point branch, we should do the same on
>> the trunk.
>>
>> Cheers,
>>
>> Les
>
Re: Next release
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I don't see why the struts 2 stuff cannot make it into this release.
Regards,
Alan
On Dec 9, 2010, at 2:27 PM, Les Hazlewood wrote:
> There are a few issues that have come in the last week that might
> justify a quick point release. I just created a 1.1.x branch to
> account for any bugs we might want to fix in a point release (if we
> actually do one).
>
> With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all
> forward-incompatible API changes and enhancements can go in there
> (unless anyone feels otherwise). We just need to know that if we
> apply any patches to the 1.1.x point branch, we should do the same on
> the trunk.
>
> Cheers,
>
> Les
Re: Next release
Posted by Les Hazlewood <lh...@apache.org>.
There are a few issues that have come in the last week that might
justify a quick point release. I just created a 1.1.x branch to
account for any bugs we might want to fix in a point release (if we
actually do one).
With that there, I'm moving the trunk to reflect 1.2-SNAPSHOT so all
forward-incompatible API changes and enhancements can go in there
(unless anyone feels otherwise). We just need to know that if we
apply any patches to the 1.1.x point branch, we should do the same on
the trunk.
Cheers,
Les
Re: Next release
Posted by Kalle Korhonen <ka...@gmail.com>.
I'm pretty busy just before the holidays. I don't see a burning need
for a point release but will certainly support it if you think it's
worth the effort. Did you have some specific issues in mind that you'd
like to get into a release?
Kalle
On Mon, Dec 6, 2010 at 11:07 AM, Les Hazlewood <lh...@apache.org> wrote:
> Do you guys wanna try to get out at least a point release to clear out
> as many issues as we can before the holidays? I think it'd be a good
> idea. Any ideas?
>
> Regards,
>
> Les
>