[sakai2-tcc] in a couple of hours - TCC - CLECC bi-weekly meeting

[Neal Caidin]

Oh yeah, almost forgot this one:

* Public discussion on Rwiki - best way to proceed?


On Mar 6, 2013, at 8:02 AM, Neal Caidin <nealcaidin at sakaifoundation.org> wrote:

> 10 am Eastern / 2 pm GMT
> 
> Any other agenda items? 
> 
> Here are a couple of more I thought of:
> 
> * Best way to publish the SurveyMonkey survey on CLE upgrade information to community (e.g. wait for conference or do this before conference?)
> * Any concerns about me doing a 2.9 CLE demo over webinar pre-Apereo conference? Best way to time it?
> * Planning new survey(s)?  Community participation survey? Tool needs survey? etc.
> 
> Thanks,
> Neal
> 
> On Mar 5, 2013, at 7:55 AM, Neal Caidin <nealcaidin at sakaifoundation.org> wrote:
> 
>> Hey
>> 
>> My plan is to send out to the technical lists - prod, qa, and dev, etc. that the schedule is to complete development by the end of this month, so we have about a month to do QA and fix bugs that come up from that process with a target date of end of April/ beginning of May for a release. To the non-technical lists I will send out that we have a target date of end of April / beginning of May.
>>  
>> 
>> Let's discuss at our meeting tomorrow, Wednesday, March 6 at 10 am Eastern / 3 pm GMT. We may also want to discuss process for releases both from a technical perspective and a schedule/quality perspective.
>> 
>> Default Dial-in Number:+1-734-418-9028 
>> 
>> Your Conference Code: 8373263 
>> 
>> Join Online: 
>> https://apps.calliflower.com/myconference/8373263 
>> 
>> Find a Dial in number in your city: 
>> https://apps.calliflower.com/account/call_in_numbers?organizer=328940
>> 
>> Skype:
>> Add ‘calliflowerskype’ as a contact in Skype.  You can then call Calliflower directly from Skype. 
>> 
>> Cheers,
>> Neal
>> 
>> 
>> On Feb 28, 2013, at 4:55 PM, "Berg, Alan" <A.M.Berg at uva.nl> wrote:
>> 
>>> As long as it is clear on the front of the .qa server what the rev is and you can find the same information back in Jiras plus its filters the administrative paper work is done.
>>> 
>>> 
>>> Regards Alan,
>>> 
>>> Sent from somewhere interesting via a Mobile device.
>>> 
>>> 
>>> 
>>> -------- Original message --------
>>> Subject: Re: [sakai2-tcc] [cle-release-team] Strawperson schedule for CLE 2.9.2 
>>> From: "Maurer, Christopher Wayne" <chmaurer at iupui.edu> 
>>> To: Neal Caidin <nealcaidin at sakaifoundation.org>,Steve Swinsburg <steve.swinsburg at gmail.com> 
>>> CC: sakai2-tcc Committee <sakai2-tcc at collab.sakaiproject.org>,"cle-release-team at collab.sakaiproject.org" <cle-release-team at collab.sakaiproject.org> 
>>> 
>>> 
>>> I think at this point, the number of QA servers are so small, that it doesn't really matter.  We're all flexible (hopefully) enough to make any accommodations needed for the process.
>>> I normally build from a tag, but I can just as easily build from a branch with a rev#.  Simple script change for me.
>>> Plus, I would say that unless it is someone really urgently planning for a release, no one uses those beta or rc tags for anything.
>>> 
>>> Chris
>>> 
>>> From: Neal Caidin <nealcaidin at sakaifoundation.org>
>>> Date: Thursday, February 28, 2013 4:28 PM
>>> To: Steve Swinsburg <steve.swinsburg at gmail.com>
>>> Cc: sakai2-tcc Committee <sakai2-tcc at collab.sakaiproject.org>, "cle-release-team at collab.sakaiproject.org" <cle-release-team at collab.sakaiproject.org>
>>> Subject: Re: [sakai2-tcc] [cle-release-team] Strawperson schedule for CLE 2.9.2
>>> 
>>> I think that may have been what Matt did for 2.9.1. 
>> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130306/3c77f264/attachment-0001.html