Difference between revisions of "Udig round the world sprint"

Revision as of 05:56, 12 December 2008

Udig round the world - code sprint

There's a plan afoot to take a couple of days to do a code sprint on uDig trunk (aka 1.2). Since doing the sprint in one place is too much to organize, plan and fund, the idea is to spend the time working on IRC. The goal is to push uDig trunk towards stability since it uses newer versions of GeoTools and Eclipse which have fixed many bugs and provide more capabilities.

There is a strong desire to prepare the code sprint with a bug festival. The bug fest would use a new release of uDig and try to break it in as many ways as possible and file those bugs. The code sprint could then aim to triage the bugs, pick areas that need work, and clean that code to fix the bugs.

This event was born out of this email thread: http://lists.refractions.net/pipermail/udig-devel/2008-December/013591.html

This code sprint will take place mostly in IRC via udig's IRC channel.

Dates

Proposed date for the sprint is 16-17th of January.

Attending people

Andrea Antonello
Silvia Franceschi
Harry Bullen
Ugo Taddei
Mauricio Pazos
Aitor Lertxundi
Eric Jarvies - Cabo San Lucas, Baja California Sur, Mexico

add yourself here

Preparatory Bug Fest

Prior to the code sprint, we want to find all of the critical bugs, and many other bugs.

A new uDig trunk(pre1.2) release is required

Someone needs to step up and do a release to build and package the latest trunk for XP/Vista, OS X, and Linux.

(Links to the release version to appear here soon.) [actually, we should just point to the uDig download page]

What will be tested before the sprint on the released version

Everyone gets to try and break uDig their own way. For more structured examination, we can accumulate ideas here.

We need to go through the uDig tutorials; these cover the functionality we need to work in order to have the product function.

Just going through this in order and listing any problems an amazing help (we can do the list in the next section).

We can list other ideas for issues to test in the table below.

TASK	CHECKED BY
Make a set of shapefiles available. Best is to use shapefile containing exotic charsets like those used by italians or german or korean	I can provide a set of shapefiles(Point, Path, and Polygon), along with PostgreSQL(dB) and Geoserver(WMS) access to the same maps/layers(en español). --Ericjarvies 13:32, 12 December 2008 (UTC)
Loading of data without prj	meep
Selection of data and sorting in the table view	1. On OS X PPC/x86, when editing PostgreSQL/PostGIS layers, changes are not saved, and a nasty loopy bug is introduced, requiring restart of uDig. 2. Need to be able to adjust column width and rearrange columns, wherein user may exit table view, return to table view, without having those columns return to their previous state. --Ericjarvies 13:32, 12 December 2008 (UTC)
Create a project, save it, restart udig with project. Move the project folder and reopen it.	meep
...add here your thought... be mean!

Issues with the tutorials

If you use the released uDig to go through the tutorials, but don't have time or know how to fix the wiki text and file JIRA tasks, please list issues you run into below.

Tutorial issues:

 * add your issue here

The Code Sprint

Triage: Tasks that were chosen to be fixed during the sprint

to be defined

@@ Line 51: / Line 51: @@
 Just going through this in order and listing any problems an amazing help (we can do the list in the next section).
+We can list other ideas for issues to test in the table below.
---
-Let's use that as a base. But since using always the same moves and the same dataset leads to always the same unseen errors, let's also fill a table with further thoughts as they come:
 {| border="1" cellpadding="2" class="wikitable"
@@ Line 76: / Line 72: @@
 |}
+=== Issues with the tutorials ===
+If you use the released uDig to go through the tutorials, but don't have time or know how to fix the wiki text and file JIRA tasks, please list issues you run into below.
+Tutorial issues:
+  * ''add your issue here''