[Contrib: Evaluation System] QA Effort for the Evaluation System

Adam Marshall adam.marshall at oucs.ox.ac.uk
Mon Jun 28 03:52:28 PDT 2010


I'm happy for a tag to be cut "now", as it happens we've just updated our build from trunk but havent gone live yet. Oxford should be able to kick-start the QA process as we'll be going through all our known issues (about 30 I think, all present in Jira) to check if they are still present (& will update Jira accordingly).

adam

| -----Original Message-----
| From: evaluation-bounces at collab.sakaiproject.org [mailto:evaluation-
| bounces at collab.sakaiproject.org] On Behalf Of Nicola Monat-Jacobs
| Sent: 26 June 2010 00:08
| To: evaluation
| Subject: [Contrib: Evaluation System] QA Effort for the Evaluation
| System
| 
| This week I was given the go-ahead to spend a few hours each week on
| EvalSys QA coordination efforts, as I offered in Denver. I don't want
| to step on any toes, but I have some suggestions on how we might
| precede.
| 
| I've been following the thread on merging EVALSYS-861 into trunk with
| interest and I think the suggestions from Adam, Aaron and Jim all make
| sense and seem to be in line with our conversations from Denver.
| 
| The real sticking point relates back to whether or not developers can
| commit to trunk without approval (partial or unanimous) from the newly-
| anointed PMC, which ultimately relates back to, I think, QA.
| 
| As we all know, without some oversight, trunk can become hazardous to
| the health of institutions running EvalSys, but waiting for the 4 very
| busy people on the PMC to fully review something before check-in risks
| putting us back where we started: with no forward motion.
| 
| I'd like to propose the solution offered in Denver by (I think) Stephen
| M. Let's cut an RC tag right now - it doesn't have to be perfect
| (should build though :) ), but it will give institutions something to
| run that isn't trunk and can be the 'go to' check out for those looking
| to work with EvalSys. It almost doesn't matter which rev it is, waiting
| is worse at this point then picking the wrong rev, I think.
| 
| Then, I can work with those groups from Denver who were willing to do
| QA and develop processes, Test Plans and a repeatable approach for QA
| going forward.
| 
| I agree with Aaron that every change (to trunk or whatever) should have
| a JIRA going forward. I'd also like to request that whoever has the
| magic to hook our JIRA project up with SVN should perform that
| particular incantation, if possible.
| 
| Bug fixes will need to be committed to both trunk and the tag, just
| like Sakai and other mature projects. I'd like to to take those efforts
| as a model for ours, if possible. I do have some process questions
| though, since I'm not intimately familiar with the mechanics of the
| normal Sakai QA process:
| 
| Once an RC tag is cut, and patches need to be made, I assume those
| patches aren't made to the tag (since that sort of goes against the
| nature of a tag). Are they normally made against a corresponding
| branch? We don't want to hold up dev work in trunk, but I assume
| patches will need to be made to graduate from RC to actual release.
| 
| Additionally, I'm happy to cut the RC tag, if someone can give me
| permission to do so. I also have limited permissions in JIRA, will
| probably need to be able to edit versions and assign issues..... I
| should probably go to Anthony with this, right, unless anyone has any
| objections?
| 
| I also think Aaron's most recent email about what types of commits
| require what kind of communication is great and should be the model we
| follow, regardless of what form QA takes.
| 
| Please let me know your thoughts!
| 
| Thanks,
| 
| Nicola Monat-Jacobs
| Senior Technical Manager
| The Longsight Group
| nicola at longsight.com
| 
| 
| 
| 
| 
| _______________________________________________
| evaluation mailing list
| evaluation at collab.sakaiproject.org
| http://collab.sakaiproject.org/mailman/listinfo/evaluation
| 
| TO UNSUBSCRIBE: send email to evaluation-
| unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"


More information about the evaluation mailing list