Hi,
by the discussion we had so far it seems the following recipe
should satisfy most needs:
- two days format (Friday and Saturday) with people free to continue
the following days if they are having fun
- a small set of core developers do a very fast full scan of the
open issues marking the obvious ones, that is, closing the ones
we're sure have been dealt with already, and marking as not done
the ones we're sure have not been implemented.
This part should take no more than half a day.
- everybody goes thought the remaining jiras and check if they are
still valid, and ask the reporter about more information if
the issue is hard to reproduce
- the tool used for collaboration is a google spreadsheet in
which we mark who's doing what and the status of each jira
(un-processed, closed, verified, needs more info)
The week after the sprint we go through all the ones that needed
more info and if it's not there we'll close them as "cannot reproduce"
Possible dates:
- Nov 13-14
- Nov 20-21
- Nov 27-28
- Dec 4-5
Can everybody say in which of the above dates he can participate?
I can participate in all of them besides Nov 20-21 (and 20-21 too,
but I'll be away half a day the 20)
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Hi,
Nice plans 
I dont know what will be tomorow, so I cant say which date is
beter for me, but Nov 13-14 I will be avaible just at night (CET time from
21:00 till I fell asleep maximally at about 3:00).
PS: in that excel/ooffice calc document will be first row with ticket number I
assume. Some other row would be fine if will represent autogenerated formula
for url to ticket. Just suggestion.
On Monday 09 November 2009 11:36:02 Andrea Aime wrote:
Hi,
by the discussion we had so far it seems the following recipe
should satisfy most needs:
- two days format (Friday and Saturday) with people free to continue
the following days if they are having fun
- a small set of core developers do a very fast full scan of the
open issues marking the obvious ones, that is, closing the ones
we're sure have been dealt with already, and marking as not done
the ones we're sure have not been implemented.
This part should take no more than half a day.
- everybody goes thought the remaining jiras and check if they are
still valid, and ask the reporter about more information if
the issue is hard to reproduce
- the tool used for collaboration is a google spreadsheet in
which we mark who's doing what and the status of each jira
(un-processed, closed, verified, needs more info)
The week after the sprint we go through all the ones that needed
more info and if it's not there we'll close them as "cannot reproduce"
Possible dates:
- Nov 13-14
- Nov 20-21
- Nov 27-28
- Dec 4-5
Can everybody say in which of the above dates he can participate?
I can participate in all of them besides Nov 20-21 (and 20-21 too,
but I'll be away half a day the 20)
Cheers
Andrea
--
Odborník na všetko je zlý odborník. Ja sa snažím byť výnimkou potvrdzujúcou
pravidlo.
Ľubomír Varga ha scritto:
Hi,
Nice plans I dont know what will be tomorow, so I cant say which date is beter for me, but Nov 13-14 I will be avaible just at night (CET time from 21:00 till I fell asleep maximally at about 3:00).
PS: in that excel/ooffice calc document will be first row with ticket number I assume. Some other row would be fine if will represent autogenerated formula for url to ticket. Just suggestion.
Following David suggestion we can export an Excel sheet that can be then moved to Google documents. I've prepared a link to all the open issues
with a simplified column layout:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+GEOS+AND+resolution+%3D+Unresolved+ORDER+BY+key+ASC%2C+priority+DESC
Using the "Views"/"Excel (current fields)" link we can grab a xls
to use in Google.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I think 27-28 may be best for me. Could probably find some 20-21 and Dec 4-5 though, and don't let me be the blocker, I can probably only put in a half day.
Andrea Aime wrote:
Hi,
by the discussion we had so far it seems the following recipe
should satisfy most needs:
- two days format (Friday and Saturday) with people free to continue
the following days if they are having fun
- a small set of core developers do a very fast full scan of the
open issues marking the obvious ones, that is, closing the ones
we're sure have been dealt with already, and marking as not done
the ones we're sure have not been implemented.
This part should take no more than half a day.
- everybody goes thought the remaining jiras and check if they are
still valid, and ask the reporter about more information if
the issue is hard to reproduce
- the tool used for collaboration is a google spreadsheet in
which we mark who's doing what and the status of each jira
(un-processed, closed, verified, needs more info)
The week after the sprint we go through all the ones that needed
more info and if it's not there we'll close them as "cannot reproduce"
Possible dates:
- Nov 13-14
- Nov 20-21
- Nov 27-28
- Dec 4-5
Can everybody say in which of the above dates he can participate?
I can participate in all of them besides Nov 20-21 (and 20-21 too,
but I'll be away half a day the 20)
Cheers
Andrea
--
Chris Holmes
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Sorry for chiming in late with a date. Any of the last three will work for me. I guess I prefer Nov 27-28 as well.
-Justin
Andrea Aime wrote:
Hi,
by the discussion we had so far it seems the following recipe
should satisfy most needs:
- two days format (Friday and Saturday) with people free to continue
the following days if they are having fun
- a small set of core developers do a very fast full scan of the
open issues marking the obvious ones, that is, closing the ones
we're sure have been dealt with already, and marking as not done
the ones we're sure have not been implemented.
This part should take no more than half a day.
- everybody goes thought the remaining jiras and check if they are
still valid, and ask the reporter about more information if
the issue is hard to reproduce
- the tool used for collaboration is a google spreadsheet in
which we mark who's doing what and the status of each jira
(un-processed, closed, verified, needs more info)
The week after the sprint we go through all the ones that needed
more info and if it's not there we'll close them as "cannot reproduce"
Possible dates:
- Nov 13-14
- Nov 20-21
- Nov 27-28
- Dec 4-5
Can everybody say in which of the above dates he can participate?
I can participate in all of them besides Nov 20-21 (and 20-21 too,
but I'll be away half a day the 20)
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.