What is Sakai QA? Alan Berg, Interim QA Director, Sakai Foundation Anthony Whyte, Release manager,...

Preview:

Citation preview

What is Sakai QA?

Alan Berg, Interim QA Director, Sakai Foundation

Anthony Whyte, Release manager, Sakai Foundation

Aaron Zeckoski, Software Engineer, Unicon and Maint team lead, Sakai

Agenda

• The Release Management Process• Quality Assurance • QA boundaries• Current Automation• Work in progress

• The Maintenance Team • How to get involved

March 2010 2European Sakai Conference – Valencia - Spain..

The Release Management ProcessAnd now here’s a…

March 2010 European Sakai Conference – Valencia - Spain.. 3

Quality AssuranceAnd now here’s a…

March 2010 European Sakai Conference – Valencia - Spain.. 4

Help out with QA for 2.7• http://confluence.sakaiproject.org/display/QA/QA+Testers+Wall• http://confluence.sakaiproject.org/display/QA/2.7.0+Changes

QA Boundaries

Making life predictable

QA Boundaries• http://confluence.sakaiproject.org/display/QA/QA+Milestone+Boundries• Define basic measurable criteria for when to cross boundaries• Work in progress• Expect product council to be more active in definitions later.• Alpha, beta, release candidate, general availabilty• Alpha = Not functionally frozen• Alpha => Beta

• Frozen state, no 2.x.x dependencies in pom files.• Beta - Cross cutting concerns reviewed

• Security review• Log review• Static code review• Special characters• As much functional code coverage as possible• Review of Jira (Maintenance team/QA)• 2.7 process not perfect, lack QA resources• Large amount of historic maintenance hidden in the bug database

Beta to Release Candidate

• Beta's occur once every two weeks. • A release candidate transition occurs after there are no

outstanding blockers and all critical issues have been assigned with a clear time to finish.

• The Executive Director can override this criteria for specific Jira's.

• All micro defects from the code reviews needs to have been removed.

• During this period of time QA performs as many functional tests as possible and signals any logistic issues.

Greater QA resources = Quicker transition from beta/RC

Release Candidate to General Availability

• Tagging is driven by the cleaning up of code. The longest time between tagging is 3 weeks. If this not achievable due the lack of resources then the Release Manager signals this to the community and the Executive Director and the Executive Director makes an appeal for resources.

• The Executive Director accepts that the Sakai final tag based on a memo from the QA director with comments from the Release Manager.

• The final tag can only be cut if there no blockers. • All significant issues are described in the release documents. • The product council is informed of the known issues document

and have the right to recommend extra release candidates. No issue is left unassigned.

General Availability

• There is a clear relationship between QA and early adopters. QA is actively involved, log files are parsed for new errors, data is collected over usage.

• Early adopters help form the maintenance teams priorities.

• The first minor tag is released within a month of the major tag.

• The criteria for acceptance of a minor tag is defined.

QA Automation

• Historically, static code review• Work in progress• Move towards active testing nightly• Corey/ Automated functional testing• Continuous builds• Stress testing• Need time to automate after 2.7 released

Automation links• Positioning Paper

• http://confluence.sakaiproject.org/display/QA/Positioning+Paper+QA

• Daily reports• http://qa1-nl.sakaiproject.org/codereview/

• Work in progress• http://builds.sakaiproject.org/

• Idea’s page• http://confluence.sakaiproject.org/display/QA/QA+improvement

• QA Contrib• https://source.sakaiproject.org/contrib/qa/trunk/

• Sonar – David Haines• http://sonar.codehaus.org/

Plug for the Sakai Book

And now here’s a…

March 2010 European Sakai Conference – Valencia - Spain.. 13

http://www.packtpub.com/sakai-courseware-management-the-official-guide

The Maintenance TeamAnd now here’s a…

March 2010 European Sakai Conference – Valencia - Spain.. 14

MT (maint team)

• http://confluence.sakaiproject.org/display/MNT

March 2010 European Sakai Conference – Valencia - Spain.. 15

How to get involvedAnd now here’s a…

March 2010 European Sakai Conference – Valencia - Spain.. 16

Blood and Treasure

BLOOD TREASURE

March 2010 European Sakai Conference – Valencia - Spain.. 17

3 main ways

• Get to work• Assets (people) and Resources (hardware)• MT, QA, RM,

• Pay your dues• Foundation subscription

• Commercial Buy In• Commercial partners and support programs

March 2010 European Sakai Conference – Valencia - Spain.. 18

Buying product development

• “How do you support Sakai QA/development?”

• Commercial development programs

• May also benefit the community

• Make contributing the code back part of the contract

http://sakaiproject.org/commercial-support

March 2010 European Sakai Conference – Valencia - Spain.. 19

Contributes all code back as requested by clienthttp://longsight.com/contact/

Sakai Skin Manager, Sakai Maps and the Sakai Knowledge Basehttp://sakaitools.edia.nl

http://www.psybergate.co.za

Unitech

• http://www.unitech.com.ar/• Sakai Corrective Support• Monthly subscription service• Multiple levels (higher cost for more support)• Email and phone based• Can be used for local or community fixes• Contact: sakai@unitech.com.ar, judithl@unitech.com.ar

March 2010 European Sakai Conference – Valencia - Spain.. 20

rSmart

• http://www.rsmart.com/sakai/learn-more• Enterprise Support Subscription• 2nd and 3rd tier support for you local instance

• Hosting services• Tool development

• OSP tools, Xslt Portal, Websphere and DB2 support, Virus scanning in content hosting, Elluminate Integration, Icodeon Integration

• Contact: http://www.rsmart.com/sakai/learn-more/service-support

March 2010 European Sakai Conference – Valencia - Spain.. 21

Unicon• http://www.unicon.net/services/sakai/support

• Cooperative Development/Support for Sakai• Yearly subscription, multiple levels• All development (bugs and features) is done

with and goes back to the Sakai community• Includes local support and assistance

• Hosting and contract development• Contact: Charise Arrowood (Webinars)

March 2010 European Sakai Conference – Valencia - Spain.. 22

GET INVOLVED!

March 2010 European Sakai Conference – Valencia - Spain.. 23

Questions and maybe some Answers

March 2010 European Sakai Conference – Valencia - Spain.. 24

Recommended