Difference between revisions of "Udig the 10 minutes bug sprint"

From OSGeo
Jump to navigation Jump to search
(Anthony and Frankline are just starting with uDIG, working with Craig Taverner)
Line 56: Line 56:
* Jesse Eichar - devel
* Jesse Eichar - devel
* Craig Taverner - testing (+devel?)
* Craig Taverner - testing (+devel?)
* Anthony Wachira - testing
* Frankline Ogongi - testing
* ...add yourself here
* ...add yourself here

Revision as of 08:42, 11 March 2009


Dear community of udig developers and users (and all osgeo supporters).

We are delighted to propose you the 10 minutes bug sprint!!

What is the 10 minutes code sprint?

A code sprint in which bugs and feature requests will be fixed that are supposed to take only 10 minutes to the involved developer (in a perfect world).

What will it gain?

  • Many small bugs fixed that make users very happy.
  • Lots of satisfaction for the developers that are involved that will smash lots of bugs.
  • A nice and clean JIRA list.
  • All in all a happy community.

When will it be?

The sprint will cover Saturday and Sunday the 14th and 15th of March 2009. As usual for uDig sprints if not defined else, it will take place in all-around-the-world IRC sessions, with Sydney giving the good start push. :)

Further informations

A cleanup of the JIRA issues list has been started and should be finished in one day or so.

A first result we gained can be seen in the list of components, which has passed from users unreadable format of more than 30 categories to a more content based set of 14 categories.

for developers

The aim is to isolate a list of bugs with that only caracteristic: it should be solvable in more or less 10 minutes.

Those bugs are going to be marked with fix version UDIG 1.2.M3 and will be available to the developers during the code sprint at this link.

for users

The aim is that to make it easier for users to report bugs and assigning them to a category. The above linked page shows the list of categories and a funny description through which Jody helps us to decide.

for testers

We are incurring in many bugs of which we are not sure if they are still bugs. So this time testers will be even more important, in order to go through the bugs list and help to decide if the issue is still a bug or if it can be closed. So please testers, come and help!

roadmap page

Also, a roadmap wiki page has been setup (still in progress) to keep under control the bugs list and their evolution.

attending people

Please add yourself here in order to know on who we can count on. Any time and any time interval will be of help to the community, so jump by even if you have just a couple of hours!

  • Andrea Antonello - devel
  • Silvia Franceschi - testing
  • Jody - devel
  • Emily - devel
  • Jesse Eichar - devel
  • Craig Taverner - testing (+devel?)
  • Anthony Wachira - testing
  • Frankline Ogongi - testing
  • ...add yourself here