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
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
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
I kind of liked our plan of making sure the pull request was mentioned in Jira and then closing the ticket - i.e. I don’t think we should wait a year on many of our “stalled” pull requests.
Given that we have a 2 month release tick/tock thing going on - why not close tickets as part of each stable release.
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
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
My thought is that closing outright is a bit much. If the ticket is invalid or irrelevant that is one thing, but if it’s still valid and just lacks the resources to do act on I don’t think it should be closed. It would nice if Jira had some sort of “archive” mode but afaik it doesn’t. Perhaps we could create a special version for this purpose.
I kind of liked our plan of making sure the pull request was mentioned in Jira and then closing the ticket - i.e. I don’t think we should wait a year on many of our “stalled” pull requests.
Given that we have a 2 month release tick/tock thing going on - why not close tickets as part of each stable release.
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
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
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