[sakai2-tcc] Draft announcement for Release Candidate 01

[Neal Caidin]

Yes, we should at a minimum use http://qa29.sakaiqa.org , even if it only redirects for now.

I started investigating getting all the servers on the sakaiqa.org domain, which is still possible, but at least we have the aliases (and I kind of like the flexibility of the aliases, but maybe moving the servers on the sakaiqa.org domain is better long term).

Chuck Hedrick gave his permission to use that statement about Rutgers.

-- Neal

On Sep 25, 2012, at 4:56 PM, Matthew Jones <matthew at longsight.com> wrote:

> Hi Steve,
> 
> 1) The Longsight server is the only one I update, so it's the only one I can guarantee gets the release up on it by first and tomorrow. Since I'm doing the release, and uploading the artifacts then rolling the build. That's the only possible reason for the bias. ;) Everyone can download and deploy at their leisure once they know it exists.
> 
> 2) None of the QA servers are on 'Sakai' infrastructure. Some of them are run at IU, some at Michigan, some at Rutgers, some at Hull. I guess that's all Sakai infrastructure.
> 
> We could name the server "http://qa29.sakaiqa.org" (And this URL works it just redirects right now) and then 99% of people wouldn't know where it was being hosted. Just somewhere in the cloud, right?
> 
> On Tue, Sep 25, 2012 at 4:46 PM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> Well done all!
> 
> Quick question regarding the QA servers. Should the longsight server be the primary one listed? It may be the only one running this tag at this point in time, however, it does makes it look like it is the official Sakai supported and endorsed QA server.
> 
> Perhaps the sakaiproject QA servers (or just one) should be built with this tag before the announcement, to remove any perceived bias? After all we should be using Sakai infrastructure for this, shouldn't we?
> 
> cheers,
> Steve
> 
> 
> 
> On 26/09/2012, at 6:28 AM, Neal Caidin <nealcaidin at sakaifoundation.org> wrote:
> 
>> Hey all,
>> 
>> It looks like 2.9.0-rc01 will be built by tomorrow, Wednesday. I was originally taking the day off, but we'll see. 
>> 
>> Here is a draft announcement for the release. I am asking Chuck Hedrick if it is okay to mention Rutgers experience. I think it would be a boost to the community's confidence.
>> 
>> DRAFT - DRAFT - DRAFT 
>> 
>> Please do not distribute
>> 
>> I am happy to announce the first release candidate for the 2.9 release, 2.9.0-rc01 . The typical schedule, from the first release candidate to final release, is usually 2 or 3 more iterations of testing and bug fixing. Rutgers has been running with a 2.9.0 based on the Beta 02 version under load for several weeks, with success. A stretch goal for a 2.9.0 GA (general availability) is mid-October, a feasible date is late October/early November, and it is highly likely we will have a release before Thanksgiving. New bugs found and community participation in fixing bugs and testing fixes are the biggest factors for the release schedule. 
>> The Sakai 2.9.0-rc01 release is up at: https://qa29.longsight.com/
>> 
>> Artifacts for other qa servers are here:
>> http://source.sakaiproject.org/release/2.9.0-rc01/artifacts/
>> You can also build from source as usual from this tag:
>> https://source.sakaiproject.org/svn/sakai/tags/sakai-2.9.0-rc01/
>> This release includes about XXYYYXXX fixes that were merged from trunk as
>> verified.
>> https://jira.sakaiproject.org/browse/SAK/fixforversion/12988
>> 
>> All indies were also released as rc01.  The list above does not include
>> those fixes.
>> 
>> We originally targeted to release 2.9.0-rc01 with no blockers, but a blocker came up during the 2.9.0-rc01 build, which will be addressed with the next release candidate. Default permissions are missing when you first add the Lessons tool to a site - https://jira.sakaiproject.org/browse/LSNBLDR-114 .
>> The next release is Sakai CLE 2.9.0-rc02, targeted for October 10. 
>> 
>> [Should we mention skinning changes since this was such a big thing between b06 and b07?]
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> _______________________________________________
>> 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
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20120925/d965491a/attachment.html