[cle-release-team] Sakai CLE 2.9.3 planning

[Neal Caidin]

Okay.

I think we might have testers available during July 1 week, which could
help a bit. Keep in mind that the more things we put into the release, the
more testing we need to do. The smaller we keep it, the less testing to
still have confidence in the release. Making this call is a little bit
science and a little bit art.

Of course, if we have blockers that we can get fixed then we should do that
if we can. We need to decide on prioritization of fixes vs date. The
rationale for the 2.9.3 July release date, as I heard it, is that if we
deliver something later than July it will not be of much use to folks in
the August/September school year start.

Thanks,
Neal


On Wed, Jun 19, 2013 at 4:33 PM, Anthony Whyte <arwhyte at umich.edu> wrote:

> I expect US productivity to drop during the week of 1-5 July as people
> take time on and around Independence day.   I think scheduling esting and a
> likely second RC during the week of the 4th trends towards the heroic.  I'd
> bump the release date at least another week out.
>
> The short list highlighted in your email looks ok but it's usually the
> case that Samigo and now Lessons have more than one fix worth pushing out.
>  Have you pinged Karen and Chuck relative to 2.9.3 timing?  Chuck mentioned
> in San Diego that he wanted to push lessons fixes and perhaps one/two minor
> enhancements out quickly.  There is also the kerfuffle on list involving
> gradebook that might require addressing as well.
>
> On Thursday's release call let's discuss what in the merge queue is
> required for 2.9.3.[1]    As I mentioned to you earlier, I'm out 27-30 June.
>
> Cheers,
>
> Anth
>
> [1] Merge queue (n=24): https://jira.sakaiproject.org/issues/?filter=13703
>
>
> On Jun 19, 2013, at 3:14 PM, Neal Caidin wrote:
>
> Hi All,
>
> CLE-release-team at collab.sakaiproject.org has not been working for me. I
> hope it is now!
>
> Hi CLE Release team,
>
> Here is my thinking for a CLE 2.9.3 schedule:
>
> - week of June 24 - Merge issues and cut a 2.9.3-rc01
> - week of July 1 - Test rc01.  If necessary cut an rc02.
> - week of July 8 - CLE 2.9.3 production
>
> Here is my stupid plan for schedule and scope for CLE 2.9.3 . See what you
> think.
>
> Scope:
>
> Main purpose of CLE 2.9.3 release is to turn AntiSamy on and a few key
> fixes.
>
> * CLE 2.9.3 should have AntiSamy turned on and a handful of issues.
> Question - High or Low setting by default?  I think if it is turned on now
> it would be High by default.
> * There are two security issues already fixed and verified. Three security
> issues would need verification to get in.
> * Several translations are already verified and just need to be merged.
> * https://jira.sakaiproject.org/browse/LSNBLDR-227 - was listed as a
> blocker issue. Should be easy to include?
> * https://jira.sakaiproject.org/browse/KNL-1060 - listed as a critical
> issue, already fixed and verified.
>
> https://jira.sakaiproject.org/browse/KNL-1089 -  not looking like this
> would get done in time based on proposed schedule above?
>
> Thoughts?
>
> Thanks
>
> --
> 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
>
>
>


-- 
Neal Caidin
Sakai CLE Community Coordinator
nealcaidin at sakaifoundation.org
skype: nealkdin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130619/c156d4bf/attachment.html