headers
Kalle Korhonen | 28 Oct 2010 19:13
Picon
Gravatar

Re: [VOTE] Release Apache Shiro version 1.1.0

On Thu, Oct 28, 2010 at 9:59 AM, Les Hazlewood <les@...> wrote:
> -1 at the moment because I think this is a bit premature.  I think
> when attempting a release, we should at least have a quick email to
> ask the other devs if there's anything left that needs to be resolved
> before we can take a vote.

This was discussed on private.

> For example, there were a lot of issues moved to 1.2, but SHIRO-186
> and SHIRO-197 have both been implemented but not yet resolved.  I left
> them open on purpose in case we needed to do some additional work
> based on users' testing.  Since we've received no feedback for them,
> they can be marked resolved and included in 1.1.

I did ask you before and you can still mark them as resolved.

> Just a quick "hey, let's try to cut a release on Friday - let's clean
> up anything that might need to happen in the next day or two" would be
> nice.

Please follow the private list; I wrote "I believe the right course of
action is to expedite the 1.1.0 release plan (our first release as
a TLP) as much as possible. Shiro PMC members, please make every
effort closing down the remaining issues for 1.1.0". There were
special circumstances cutting the release which is why this was
discussed there.

Kalle
(Continue reading)

Permalink | Reply |
headers
Les Hazlewood | 28 Oct 2010 19:39
Picon
Favicon

Re: [VOTE] Release Apache Shiro version 1.1.0

On Thu, Oct 28, 2010 at 10:13 AM, Kalle Korhonen
<kalle.o.korhonen@...> wrote:

>> -1 at the moment because I think this is a bit premature.  I think
>> when attempting a release, we should at least have a quick email to
>> ask the other devs if there's anything left that needs to be resolved
>> before we can take a vote.
>
> This was discussed on private.

That was the case, but because of a critical work deadline, I've been
out of the loop for the last 36 hours and the comment was embedded in
a long string of emails that I haven't fully caught up on (this
morning I've had my first bit of 'breathing room').

In the past, the project team has always dedicated a thread for
discussing prep for a release, and I assumed it would be the same this
time around and not embedded in a different thread.  I'm just asking
that we have such a dedicated discussion thread as a course of action
for anything that will probably lead to a vote ('e.g. 'Upcoming
Release: blah') - just so all members can clearly distinguish things
of this level of importance before being surprised by a full vote.

Alan's comment about the crowd source code is another example of why
this is a good idea.  That should have been surfaced in the release
discussion thread, not the vote thread IMO.

This isn't strictly required of course - just a requested courtesy.
The [VOTE] thread itself is obviously enough of an attention grabber
to catch any outstanding issues (as this one clearly did).
(Continue reading)

Permalink | Reply |
headers
Les Hazlewood | 28 Oct 2010 19:44
Picon
Favicon

Re: [VOTE] Release Apache Shiro version 1.1.0

Also, I agree with Alan's comments about the crowd support.  We don't
know 100% if that's totally compatible with the ASF 2.0 license based
on the crowd libraries.  We may be, but we'd better leave it out for
the release, just in case, and move it to 1.2.

Kalle, do you want to handle that while I address my Jira issues?  If
not, I'd be happy to do it afterwards.

Les
Permalink | Reply |
headers
Kalle Korhonen | 28 Oct 2010 19:54
Picon
Gravatar

Re: [VOTE] Release Apache Shiro version 1.1.0

The code Alan wrote is certainly Apache licensed. We have no
dependencies to Crowd at the moment so I don't see any issue here.

Kalle

On Thu, Oct 28, 2010 at 10:44 AM, Les Hazlewood <lhazlewood@...> wrote:
> Also, I agree with Alan's comments about the crowd support.  We don't
> know 100% if that's totally compatible with the ASF 2.0 license based
> on the crowd libraries.  We may be, but we'd better leave it out for
> the release, just in case, and move it to 1.2.
>
> Kalle, do you want to handle that while I address my Jira issues?  If
> not, I'd be happy to do it afterwards.
>
> Les
>
Permalink | Reply |
headers
Les Hazlewood | 28 Oct 2010 20:06
Picon
Favicon

Re: [VOTE] Release Apache Shiro version 1.1.0

Ok, but why did Alan (who wrote the code) recommend that it stay out
of this release?  If it's not due to licensing issues, then it's
probably because it may not have been decently vetted and that it may
be changed enough later such that we could have likely
backwards-incompatibility issues.

If this is the reason, then it sounds like a good enough of one to me
to keep it out of the next minor release.

How hard is it to just tag what we have and delete that module?  Do
you have any objections Kalle?

Les
Permalink | Reply |
headers
Alan D. Cabrera | 28 Oct 2010 21:24

Re: [VOTE] Release Apache Shiro version 1.1.0


On Oct 28, 2010, at 11:06 AM, Les Hazlewood wrote:

> Ok, but why did Alan (who wrote the code) recommend that it stay out
> of this release?  If it's not due to licensing issues, then it's
> probably because it may not have been decently vetted and that it may
> be changed enough later such that we could have likely
> backwards-incompatibility issues.
> 
> If this is the reason, then it sounds like a good enough of one to me
> to keep it out of the next minor release.
> 
> How hard is it to just tag what we have and delete that module?  Do
> you have any objections Kalle?

I just wanted to make sure we had consensus on what we do with the Crowd realm before we released it.  If it's
"commented out" by removing the module entry in the tag then I think the code should be totally removed. 
IIUC, it's the tag that Apache is releasing and the artifacts are nice things that we do for our community.  I
recommend that we branch 1.1, remove crowd, and make any tags we want off of that.

Regards,
Alan
Permalink | Reply |

Gmane