[sakai2-tcc] [cle-release-team] Strawperson schedule for CLE 2.9.2

Maurer, Christopher Wayne chmaurer at iupui.edu
Thu Feb 28 13:42:02 PST 2013


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<mailto:nealcaidin at sakaifoundation.org>>
Date: Thursday, February 28, 2013 4:28 PM
To: Steve Swinsburg <steve.swinsburg at gmail.com<mailto:steve.swinsburg at gmail.com>>
Cc: sakai2-tcc Committee <sakai2-tcc at collab.sakaiproject.org<mailto:sakai2-tcc at collab.sakaiproject.org>>, "cle-release-team at collab.sakaiproject.org<mailto:cle-release-team at collab.sakaiproject.org>" <cle-release-team at collab.sakaiproject.org<mailto: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. I don't see a downside to it, unless there is any issue with bringing up QA servers or issues with folks downloading and testing locally. Are there clear instructions for doing that? I've found it helpful sometimes to run Sakai locally so I can muck around with properties. Alan B. sometimes runs through his own tests I believe. I imagine others do this too.

What do others think about this idea? It has a clear positive aspect of speeding up the process, are there any downsides?

-- Neal

On Feb 28, 2013, at 3:31 PM, Steve Swinsburg <steve.swinsburg at gmail.com<mailto:steve.swinsburg at gmail.com>> wrote:

I dont think that RC's are necessary for branches and it just slows the process down since they take a while to create. The branch should be in a constant state of readiness for tagging. If there is some major bug identified that affects the branch, fix it, merge it, rebuild the branch. Can the QA servers run branches? If they took the branch at some known revision that would be ideal.


On Fri, Mar 1, 2013 at 3:27 AM, Neal Caidin <nealcaidin at sakaifoundation.org<mailto:nealcaidin at sakaifoundation.org>> wrote:
[cle and tcc]

Hi All,

We had an initial discussion of the milestones for a 2.9.2 release on the CLE team call today.  Once we agree (TCC and CLE teams) that this seems reasonable, I can let the Community know our plans/ targets. I would use less detail for communication to the Community.

Strawperson schedule - for discussion
-------------------------------------------------------
up till March 29 - issues merged, development / fixes/patches, QA testing on trunk to verify fixed issues, etc.
2.9.x merges complete - March 29
2.9.2 testing on 2.9.x (i.e. beta testing) - week of April 1
2.9.x testing complete (i.e. beta testing) - April 5
2.9.2 RC-01 cut - April 8/9
2.9.2 testing - April 10 - 16
2.9.2 RC-01 testing complete - April 17
2.9.2 RC-02 cut - April 18/19
2.9.2 testing - week of April 22
2.9.2 RC-02 testing complete - April 26
2.9.2 Release and release documentation - week of April 29


Some assumptions I'm making:

* We will do beta testing on 2.9.x instead of cutting a release
* We will need two release candidates (we did for 2.9.1)
* We will build an RC01 and RC02 - but I think Matt Jones did this a different way for 2.9.1? This might need discussion, but not a huge impact on schedule either way.
* About a week for testing in between beta and release candidates
* Release documentation will be done in parallel (since this is mostly me, I feel pretty comfortable with this assumption)

Questions? Thoughts?

Cheers,

Neal Caidin

Sakai CLE Community Coordinator
nealcaidin at sakaifoundation.org<mailto:nealcaidin at sakaifoundation.org>
Skype: nealkdin
AIM: ncaidin at aol.com<mailto:ncaidin at aol.com>






_______________________________________________
cle-release-team mailing list
cle-release-team at collab.sakaiproject.org<mailto:cle-release-team at collab.sakaiproject.org>
http://collab.sakaiproject.org/mailman/listinfo/cle-release-team



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai2-tcc/attachments/20130228/20dfa20c/attachment-0001.html 


More information about the sakai2-tcc mailing list