Template:Qa sprint

What

QA Sprint days are days designated to pass QA on important and/or complex patches

When

The next QA sprint day is the 24 hours of {{{when}}}, in whatever time zone you are in.

Time conversion: [{{{start}}} Starting time] ({{{when}}} starts in Kiritimati, Christmas Island, Kiribati), [{{{stop}}} ending time] ({{{when}}} ends in Honolulu, Hawaii, United States).

Where

Wherever you happen to be.

What to do

• The QA team maintains a list of bugs they are working/QAing on the wiki page as they are working on them. Also note QA contacts added to your bugs on bugzilla.
• Suggestions can be made on IRC and priorities for QA'ing can also be discussed at the General IRC Meeting on 11th September.
• The QA team will collaborate with the bug authors to get their patches through QA - Be around to answer questions and provide follow-ups!

What can I do

• get your patches 'signed-off' so they ready for QA
• be around and help us, answer questions about patches and provide follow-ups if necessary
• suggest that your patches be prioritized on the QA list

These pages might also be of interest:

• Coding Guidelines
• Guidelines for Patch Acceptance/Rejection
• Bug-enhancement-patch Workflow
• Version Control Using Git
• Git bz configuration
• Setting Up Koha in Virtual Environment + Using That as a Development Environment

Not sure how to do it? Jump on IRC and you will probably find someone who can help you along!

Tools

• Dashboard - Koha bug dashboard
• Sandboxes If you do not have access to your own Koha instance or permissions on your system, you can use the Sandboxes set up by BibLibre (Note: best to organise this a day in advance)