Difference between revisions of "Udig round the world sprint"
| Line 40: | Line 40: | ||
Just going through this in order and listing any problems an amazing help (we can do the list in the next section). | Just going through this in order and listing any problems an amazing help (we can do the list in the next section). | ||
| + | |||
| + | |||
| + | -- | ||
| + | |||
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: | 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: | ||
| Line 58: | Line 62: | ||
|- | |- | ||
|} | |} | ||
| − | |||
== Tasks that were choosen to be fixed during the sprint == | == Tasks that were choosen to be fixed during the sprint == | ||
Revision as of 05:45, 12 December 2008
Udig round the world - code sprint
This event gets born out of this email thread: http://lists.refractions.net/pipermail/udig-devel/2008-December/013591.html
Through this event we want to give the udig trunk version a push towards stability.
This code sprint will be help mostly via udig's IRC channel.
Dates
Proposed date for the sprint is 16-17th of January.
Attending people
add yourself here
The inquiried 1.2 udig release
Volountair needed to package one. The links to it for the different operating systems will appear here soon.
What will be tested before the sprint on the released version
We need to go through the uDig tutorials; these cover the functionality we need to work in order to have the product function.
- http://udig.refractions.net/confluence/display/EN/Quickstart
- http://udig.refractions.net/confluence/display/EN/Walkthrough+1
- http://udig.refractions.net/confluence/display/EN/Walkthrough+2
Just going through this in order and listing any problems an amazing help (we can do the list in the next section).
--
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:
| 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 | no one |
| Loading of data without prj | |
| Selection of data and sorting in the table view | |
| Create a project, save it, restart udig with project. Move the project folder and reopen it. | |
| ...add here your thought... be mean! |
Tasks that were choosen to be fixed during the sprint
to be defined