[Building Sakai] Release Management Call, Thurs 11 March 2010 (recommending cancellation for this week)

[Berg, Alan]

Hi fellow hard workers,

>At this point it may make sense to get hard headed and say that 2.7 will be released as is.  Only blockers will be addressed and to be a blocker an problem has to be a defect in existing code that is serious enough to prevent people from using the release.

As always David is talking commonsense. To those of you that have time or manage resources. We have clearly defined issues in well written Jira's with clear coding objectives. Isn't this the time to surge resources so we can go to release with the best we can. I think we should aspire to eat as many critical Jira's as possible on top of the blockers.


Alan

Alan Berg
Interim QA Director - The Sakai Foundation

Senior Developer / Quality Assurance
Group Education and Research Services
Central Computer Services
University of Amsterdam

http://home.uva.nl/a.m.berg




-----Original Message-----
From: sakai-dev-bounces at collab.sakaiproject.org on behalf of David Haines
Sent: Thu 3/11/2010 16:55
To: Anthony Whyte
Cc: Sakai QA; Developers Sakai-Dev
Subject: Re: [Building Sakai] Release Management Call,Thurs 11 March 2010 (recommending cancellation for this week)
 
Comments below.

- Dave

David Haines
CTools Developer
Digital Media Commons
University of Michigan 
dlhaines at umich.edu



On Mar 11, 2010, at 7:45 AM, Anthony Whyte wrote:

> I'd like to propose that we cancel this week's meeting.  Both David, Jean-Francois and I are involved in the regional SA meeting and while I think we can make it back to UCT from our current location it may prove tough given the traffic here in Cape Town between 4-5 pm (GMT +2).
> 
> There are however a couple of issues that I'd like to highlight for discussion on list.  One involves the issue of two tools in trunk/2.7.x that have largely been abandoned from a support perspective: reports and warehouse.  I asked Alan to surface the issues on the dev and production lists since it has been suggested that these projects be dropped from the build and perhaps even removed to contrib.  This is an issue that impinges directly on RM and I am interested in people's opinions on this issue.
> 

If there aren't developers willing to take responsibility for the code and the Maintenance Team has reviewed the situation and don't feel they can take on the additional work then the tools should go out of the release and off to contrib.  Tools without someone to fix them shouldn't be allowed to complicate releasing maintained and popular tools.

> Second, it's now mid-March and there are currently over 200 open issues against 2.7.  I expect that we will now need to consider triaging this list in order to target fixes that must go into 2.7.0 Spring release against those that we can reasonably push off to 2.7.1 (June/July).  If this makes sense we should consider setting up a special call (probably more than one) to review the current outstanding issues in order to put together a set of RM/QA recommendations regarding those issues that need to be addressed.  We did this for 2.6.2/2.5.6 and found it quite useful.
> 

At this point it may make sense to get hard headed and say that 2.7 will be released as is.  Only blockers will be addressed and to be a blocker an problem has to be a defect in existing code that is serious enough to prevent people from using the release.

There is always more good stuff to put in the release.  We need to give weight to all the good stuff that already is in the release but not being used while we keep waiting for that last  1%.

Anyone want to analyze the issues that have trickled in? There probably are some best practice recommendations that could be extracted based on the problems that show up more than once.

> If people feel we need to call in today please say so on list.
> 
> Cheers,
> 
> Anthony
> 
> ____________________________
> 
> Connection Info  (if demand warrants a call)
> 
> 	. Telephone (Sakai001): +1 812 856 7060  
> 	. Internet: 156.56.240.9
> 	. Conference Code: 348#
> 	. PIN: 72524#
> 
> 
> 
> 
> 
> 
> 
>   
> 
> 
> 
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100311/cf3c1c51/attachment.html