[Geoserver-devel] Interesting ticket handling proposal on the mapserver side

GeoServer GeoServer Developer
1

Hi,

I wrote a counter-proposal:

http://lists.osgeo.org/pipermail/mapserver-dev/2014-March/013961.html

-Jukka-

···

Andrea Aime wrote:

Hi,

just seen this mail on the mapserver mailng list:

=======================================================

Hi MapServer PSC

MOTION:

To adopt the practice of automatically closing issues in the MapServer Github repository that have had no activity for more than one year.

And I start with my +1

Context:

This came up again at the Vienna Code Sprint today and there was general agreement to go ahead with this mass closing since tickets that have seen no activity in over a year are either invalid, no longer relevant, or lacking information or a champion to address them. If a ticket is automatically closed by the script but is still relevant then someone can reopen it and provide an update on its status.

Stephan Meissl and Thomas Bonfort have created a script to automatically execute this mass closing and tested it at the sprint last year. If this motion passes, this script would be run manually at regular interval every few months.

=======================================================

This is a problem we also have, ton of tickets having little or no chance

of getting resolved in the short term.

Now, while I agree we should close stuff that cannot be reproduced, I’m

rather hesitant to automatically close valid tickets just because we did not

have time to work on them.

Opinions?

Cheers

Andrea

–

==

Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK

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

2

Ciao Andrea,
as you know when we do on online bug-fix sprint (btw, when are we
going to schedule next? Separate thread I guess) I am very keen
on closing old/dangling tickets.

However, mass closing does hurt me a bit. It like pushing the dust
under the furniture to clean up the house IMHO :slight_smile:

(No offense meant for the MapServer friends!)

Regards,
Simone Giannecchini

Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK
for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 333 8128928

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

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

On Mon, Mar 24, 2014 at 5:59 PM, Rahkonen Jukka (Tike)
<jukka.rahkonen@anonymised.com> wrote:

Hi,

I wrote a counter-proposal:

http://lists.osgeo.org/pipermail/mapserver-dev/2014-March/013961.html

-Jukka-

Andrea Aime wrote:

Hi,

just seen this mail on the mapserver mailng list:

=======================================================

Hi MapServer PSC

MOTION:

To adopt the practice of automatically closing issues in the MapServer
Github repository that have had no activity for more than one year.

And I start with my +1

Context:

This came up again at the Vienna Code Sprint today and there was general
agreement to go ahead with this mass closing since tickets that have seen no
activity in over a year are either invalid, no longer relevant, or lacking
information or a champion to address them. If a ticket is automatically
closed by the script but is still relevant then someone can reopen it and
provide an update on its status.

Stephan Meissl and Thomas Bonfort have created a script to automatically
execute this mass closing and tested it at the sprint last year. If this
motion passes, this script would be run manually at regular interval every
few months.

=======================================================

This is a problem we also have, ton of tickets having little or no chance

of getting resolved in the short term.

Now, while I agree we should close stuff that cannot be reproduced, I'm

rather hesitant to automatically close valid tickets just because we did not

have time to work on them.

Opinions?

Cheers

Andrea

--

==

Meet us at GEO Business 2014! in London! Visit http://goo.gl/fES3aK

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

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

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

3

I'm with Jukka on this and I think his counter-proposal has a lot of merit. With unresolved issued that I would like to think would be fixed one day, I am not sure about the getting notice "ticket closed".

I especially like the idea of periodically asking user if issue to still a problem for tickets year old, on an annual basis.

Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.