[cle-release-team] 2.9.2 status check

[Neal Caidin]

Good points Anthony. Thanks.  

Matt says he might be able to "cut" the release by tomorrow afternoon/evening (assuming things are ready and depending on his availability). That means one QA server - Longsight.

Alan Berg says he will be available to configure his QA server on Wednesday. I haven't checked with Chuck H. yet. 

I'm finishing up the final details of the test plan. final-final details require the QA servers to be up and running. 

From these data points, I'm guessing we will be able to start testing on Thursday, but there are still a few "hanging chads" (aka final details).

FYI - My availability next week is spotty, unfortunately, including probably missing a 1/2 day Tuesday morning (Eastern Daylight), part of Wednesday afternoon, and then I'm unavailable Thursday, April 25 through April 29 (though I should be able to check in on things this day, at a minimum). I'm not sure how/if this will impact things. 

The sooner we can finalize things the better, so I can send out a call to the community asking for QA help.

Cheers,
Neal

On Apr 15, 2013, at 10:37 AM, Anthony Whyte <arwhyte at umich.edu> wrote:

> Down to 4 tickets at present, three of which are not ready to merge due to either missing info, merge conflicts or reversions due to problems.  Per the AntiSamy proposal we've got a day left before we are supposed to cut RC1.  I think we could live without both KNLs (never mind the SAKs).  
> 
> Are you guys comfortable with KNL-1051?
> 
> Finally, I think emails such as this should be public and posted to the cle-release-team.  While I appreciate the politeness that no doubt serves as the motivation behind these private posts, I think we should talk about this stuff in public.
> 
> Cheers,
> 
> Anth
> 
> 
> 
> On Apr 15, 2013, at 7:51 AM, Neal Caidin wrote:
> 
>> Hey guys,
>> 
>> It seems like BLTI 2.1.0 is merged and I think so is AntiSamy ?
>> 
>> It appears there are 1/2 dozen merges left, with one blocker:
>> 
>> https://jira.sakaiproject.org/browse/KNL-1038
>> 
>> Is this a true blocker for 2.9.2 or can we proceed without it, and fix for 2.9.3? If it gets fixed will we be ready to create RC01?
>> 
>> Thanks,
>> Neal
>> 
>