[sakai2-tcc] Proposal: CLE Team wants to release Sakai 2.9.3

John Bush jbush at anisakai.com
Thu Aug 15 13:02:13 PDT 2013


+1

On Thu, Aug 15, 2013 at 11:49 AM, Matthew Jones <matthew at longsight.com> wrote:
> +1
>
>
> On Thu, Aug 15, 2013 at 2:32 PM, Sam Ottenhoff <ottenhoff at longsight.com>
> wrote:
>>
>> There are currently no blocker bugs against the Sakai 2.9.x branch.  I
>> propose that a roll call vote be scheduled by the TCC chair on the
>> question of releasing Sakai 2.9.3.
>>
>> Sakai 2.9.3-rc05 contains a fix for SAM-973 to display proper
>> correct/incorrect GIFs for fill-in-the-blank questions done before the fix.
>>
>> Sakai 2.9.3-rc04 contains a WebDAV fix (rolling back SAK-19592).
>>
>> Sakai 2.9.3-rc03 contains fixes for LSNBLDR-276 and LSNBLDR-91.
>>
>> Sakai 2.9.3-rc02 included missed merges for SAK-23733.
>>
>> The Security WG, CLE Team, and QA Teams have all been polled by Neal and
>> no objections were made to the readiness of the release.
>>
>> The latest RC05 SAM-973 has been tested and confirmed fixed by Stanford
>> (committer), UVA, and Longsight.
>>
>> Please hold votes until the TCC chair proposes the vote.  I would
>> encourage as quick a vote as possible under our rules as a) fall term is
>> starting and b) releaser availability.
>>
>> --Sam
>>
>> _______________________________________________
>> sakai2-tcc mailing list
>> sakai2-tcc at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>>
>
>
> _______________________________________________
> sakai2-tcc mailing list
> sakai2-tcc at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai2-tcc
>



-- 
John Bush
602-490-0470

** This message is neither private nor confidential in fact the US
government is storing it in a warehouse located in Utah for future
data mining use cases should they arise. **


More information about the sakai2-tcc mailing list