[WG: Sakai QA] [DG: Teaching & Learning] [Deploying Sakai] OSP and Sakai 10

[Neal Caidin]

I'm pretty sure you are aware of the (not officially sanctioned but 
generally applied) definition of a blocker [1]. So I interpret your 
statement as meaning that if we don't commit to resolving severe 
problems with OSP, then essentially there is no such thing as an OSP 
blocker and it should be stealthed. That pretty close to your meaning?


[1] 
https://confluence.sakaiproject.org/display/MGT/Sakai+Jira+Guidelines - 
Release will not be completed until issue is resolved. An example would 
be a severe problem that bridges multiple tools, or prevents core 
functionality in one tool.


-- Neal


> Berg, Alan <mailto:A.M.Berg at uva.nl>
> January 17, 2014 at 3:39 PM
>
> If there is no definition of blocker then stealthing is a logical 
> consequence.
>
> Regards,
>
> Alan
>
> On 17 Jan 2014 21:27, Neal Caidin <neal.caidin at apereo.org> wrote:
> Well, for example, in reviewing Sakai 10 critical/blockers it's 
> something that was discussed. I believe it has come up with various 
> other discussions, so it seemed like a theme worth floating and seeing 
> what others think.
>
> -- Neal
>
>
> May, Megan Marie <mailto:mmmay at iu.edu>
> January 17, 2014 at 3:12 PM
>
> Who is a "few quarters"?
>
> *From:*production-bounces at collab.sakaiproject.org 
> [mailto:production-bounces at collab.sakaiproject.org] *On Behalf Of 
> *Neal Caidin
> *Sent:* Friday, January 17, 2014 2:57 PM
> *To:* sakai-dev; Sakai QA; production at collab.sakaiproject.org; 
> sakai-user at collab.sakaiproject.org; pedagogy at collab.sakaiproject.org; 
> portfolio at collab.sakaiproject.org
> *Subject:* [Deploying Sakai] OSP and Sakai 10
>
> [dev, qa, production, sakai-user, pedagogy, portfolio]
>
> Hey All,
>
> >From a few quarters, what I'm hearing is that for Sakai 10 probably 
> no OSP issues will be considered blockers. And for OSP issues which do 
> get fixed, we need some QA commitment so that we can verify the 
> patches, otherwise even getting in those patches could be a problem, 
> from a risk perspective.
>
> Any thoughts on this? Anybody leading the charge on the current OSP 
> tool in Core or willing to step up and lead OSP QA?
>
> As an FYI, there is an exciting effort to develop a new portfolio tool 
> - 
> https://confluence.sakaiproject.org/display/OSP/Portfolios+for+the+Future+of+Sakai 
>
>
> Thanks,
> Neal
>
> -- 
> Neal Caidin
> Sakai Community Coordinator
> Apereo Foundation
> neal.caidin at apereo.org <mailto:neal.caidin at apereo.org>
> Skype me! (but let me know in advance for the first interaction) - 
> nealkdin
>

-- 
Neal Caidin
Sakai Community Coordinator
Apereo Foundation
neal.caidin at apereo.org
Skype me! (but let me know in advance for the first interaction) - nealkdin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20140117/26de3739/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: compose-unknown-contact.jpg
Type: image/jpeg
Size: 770 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-qa/attachments/20140117/26de3739/attachment.jpg