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. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
