OSGeo.org › OSGeo Software Projects › GeoServer › GeoServer - Dev

Bug fix code sprint, tentative list

Classic

List

Threaded

2 messages Options

geowolf

Bug fix code sprint, tentative list

Hi,

for max productivity during Friday's bug fix code sprint it can be useful to identify in advance some jira tickets that we could work on:

* strictly bug fixes (we cannot do new features, though improvements to the docs are welcomed)

* fix is understood, or it seems easy to fix anyways (we don't want to spend the whole day on a single ticket and then raise white flag because it's too hard to fix, or the fix is too invasive)

I had a first quick crack at a list looking at the first 150 issues that have been most recently commented on (fresh stuff) and came up with the following:

http://jira.codehaus.org/issues/?jql=project%20%3D%20GEOS%20AND%20labels%20%3D%2024xbeta-cs%20AND%20status%20%3D%20Open

As you can see I've labelled 24xbeta-cs to make them easier to find.

Other devs might want to do the same?

Cheers

Andrea

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf

Technical Lead

GeoSolutions S.A.S.

Via Poggio alle Viti 1187

55054 Massarosa (LU)

Italy

phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

http://www.geo-solutions.it

http://twitter.com/geosolutions_it

-------------------------------------------------------

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

geowolf

Re: Bug fix code sprint, tentative list

On Sun, Jul 21, 2013 at 6:31 PM, Andrea Aime <[hidden email]> wrote:

Hi,
for max productivity during Friday's bug fix code sprint it can be useful to identify in advance some jira tickets that we could work on:

* strictly bug fixes (we cannot do new features, though improvements to the docs are welcomed)

* fix is understood, or it seems easy to fix anyways (we don't want to spend the whole day on a single ticket and then raise white flag because it's too hard to fix, or the fix is too invasive)

I had a first quick crack at a list looking at the first 150 issues that have been most recently commented on (fresh stuff) and came up with the following:
http://jira.codehaus.org/issues/?jql=project%20%3D%20GEOS%20AND%20labels%20%3D%2024xbeta-cs%20AND%20status%20%3D%20Open

Btw, some clarifications on the intent of having a list here.

I don't want to setup a list force people work on specific subjects, I believe everybody should feel free to bug fix whatever

they want during the bugfix fest, otherwise it's just going to be another day at work :-)

The idea behind the list is to try and locate before hand a bunch of tickets that seem to hit some sweet spot in terms

of being actionable and relatively easy to solve, so that we don't collectively spend the first few hours to look at what

to fix (I hope we'll get some user feedback on the beta, that would be of courses prime choices).

But if people come and already know what they want to work on, that's great :-)

Users wise, please don't start labelling every ticket you care about with the 24xbeta-cs label, nothing wrong with letting us

know that you care, but if we end up with a large list of issues many of which are not properly bug fixes, require a lot

of work to be done, or require changes in dangerous to touch areas well... the value of the list will be diminished a lot.

That said, users are welcomed to participate, do you want to help us improve the docs?

I guess we need to find some easy way for Windows people to edit rst... maybe notepad++ with the right

syntax highlight (https://github.com/steenhulthin/reStructuredText_NPP)? Any other suggestion?