Message-ID: <628343077.1532.1495572190601.JavaMail.confluence@gw81> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_1531_1954583548.1495572190598" ------=_Part_1531_1954583548.1495572190598 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html 2012-02-25 Development Sprint

2012-02-25 Development Sprint

General Info<= /h2>=20

Topic: Bug Fixing Sprint 2012
Leads: =EF=BB=BFBen Wolfe
Date:<= /strong> 25 February-11 March 2012
Kickoff Meeting: = 16:00 UTC / 11:00am ET, Monday February 25th (find your timezone)

=20
=20

Group Chat

=20 =20
=20

via IRC on the #openmrs channel on fre= enode.

=20

Use this channel for ALL debugging and random questions= having to do with the sprint. Please avoid direct messaging to personal co= ntacts. If you have a question, someone else probably does too, and our geo= graphically distributed community benefits from public group discussion.

=20
=20

How to Participa= te

=20

Add your name to the list on this wiki page (with any comments about you= r availability). If you want to join after the sprint has started just join= the IRC channel mentioned above and say hello.

=20

The general process:

=20
    =20
  1. Pick a ticket from the available tickets in the top-left of the dashboa= rd.=20
      =20
    • Make sure it does not depend on a ticket that is incomplete.
    • =20
  2. =20
  3. If you have any questions about the ticket, ask on the group chat
  4. = =20
  5. Do the ticket
  6. =20
  7. Commit code and click "Committed Code" (preferred) or attach = a [patch|docs:Patches] and click "Request Code Review"
  8. =20
=20

Participants

=20 =20

Please try to attend the kickoff meeting (see above for timing)<= /strong>.

=20

How to Subm= it Bug Reports

=20

Make sure you are running a supported version of OpenMRS:=20
    =20
  • If you're unsure if your version is supported or not, you can see a lis= t of unsupported versions here: Unsu= pported Releases of OpenMRS
    We appreciate your efforts t= o report a potential bug with OpenMRS. Before you do, please ask yourself t= he following:
  • =20
=20

File a bug report<= /h3>=20

We truly appreciate your feedback, so here are a couple of options to fi= le your bug report:

=20
    =20
  1. You can file a bug report in the OpenMRS Trunk project in JIRA: File a bug report in JIRA
    Please include as much i= nformation as possible:=20
      =20
    1. A clear description of how to recreate the error, including any error m= essages shown.
    2. =20
    3. The version of OpenMRS you are using.
    4. =20
    5. The type and version of the database you are using, if known.
    6. =20
    7. If you are using any additional modules, custom templates, stylesheets,= or messages, please list them.
    8. =20
    9. If applicable, please copy and paste the full Java stack trace.
    10. =20
    11. If you have already communicated with a developer about this issue, ple= ase provide their name.
    12. =20
  2. =20
  3. If you are not comfortable creating a traditional bug report or are oth= erwise unable to do so, you may fill out this simple= bug report form
  4. =20
=20

Tickets

=20

This week's sprint:http= s://tickets.openmrs.org/secure/Dashboard.jspa?selectPageId=3D11550

= =20

General bug fixing dashboard:https://tickets.openmrs.org/secure/Dashboard.jspa?selectPageId=3D1145= 0

=20

About

=20

This sprint has the following goals:

=20
    =20
  • Fix bugs in OpenMRS and bundled modules based on community feed= back
  • =20

------=_Part_1531_1954583548.1495572190598--