[cle-release-team] Blocker or Critical?

[Matthew Jones]

I agree, critical no blocker. Though it looks to be fixed today so would be
in release if it works!
On Oct 27, 2012 3:07 PM, "Noah Botimer" <botimer at umich.edu> wrote:

> Well, we often use Blocker as a shorthand for "we really think this should
> be in the release". That's fine and we don't need to rehash all of how the
> JIRA priority values are really more like severity, but having two fields
> is more confusing than helpful. Or the various Fix/Target version
> iterations.
>
> Experience tells us it's going to be a little loose no matter what. I was
> just recalling one imperfect attempt to put some objective criteria on the
> levels for comparison with this issue.
>
> Call it Critical or call it Blocker. Mark a 2.9.1 Fix version or not. My
> opinion is that we should not consider it a 2.9.0 Blocker in that it would,
> by itself necessitate another RC. Let's just try to make sure it gets
> attention before the next tag (rc3 or 2.9.1).
>
> Thanks,
> -Noah
>
> On Oct 27, 2012, at 1:27 PM, Neal Caidin <nealcaidin at sakaifoundation.org>
> wrote:
>
> Awesome, thanks. So it sounds like this would not normally be considered a
>  blocker anyway, regardless of release timing?
>
> I'm feeling like there is momentum to start defining a 2.9.1 release
> (well, at least talking to Matt J. and Aaron Z.). Let's get 2.9.0 out and
> then we can start that discussion!
>
> - Neal
>
>
> On Sat, Oct 27, 2012 at 8:58 AM, Noah Botimer <botimer at umich.edu> wrote:
>
>> Sounds right to me, unless someone like Rutgers says this is an extreme
>> instructional issue. Remember, our criteria for Blocker have to do with
>> data loss, complete breakage, nasty security risks, etc.
>>
>> I'm personally hoping for a very quick 2.9.1. I've been in release
>> candidate paralysis for some time now. I'm anxious to solve some CKEditor
>> issues but they can't hold up the release.
>>
>> This is partly an excuse (I can work in trunk and branches), but I don't
>> want this stuff to hang in limbo forever. If it's too long between
>> work/merge, stuff gets dropped or mangled.
>>
>> Ship it, fix it, ship it.
>>
>> Thanks,
>> -Noah
>>
>> On Oct 27, 2012, at 8:31 AM, Neal Caidin <nealcaidin at sakaifoundation.org>
>> wrote:
>>
>> > Hi All,
>> >
>> > I'm not sure if this should be a critical or a blocker. Since we are so
>> close to the release of 2.9.0 , I've classified this as a critical. Does
>> that sound right?
>> >
>> > https://jira.sakaiproject.org/browse/LSNBLDR-137 - Lessons: Assignment
>> saved as draft counts as being submitted
>> >
>> > Thanks,
>> >
>> > Neal Caidin
>> >
>> > Sakai CLE Community Coordinator
>> > nealcaidin at sakaifoundation.org
>> > Skype: nealkdin
>> > AIM: ncaidin at aol.com
>> >
>> >
>> >
>> >
>> > _______________________________________________
>> > cle-release-team mailing list
>> > cle-release-team at collab.sakaiproject.org
>> > http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>>
>
>
>
> --
> Neal Caidin
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> skype: nealkdin
>
>
>
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20121027/78942693/attachment-0006.html