Mass close all improvement/new feature tickets that have not seen any progress/interest in one year?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Mass close all improvement/new feature tickets that have not seen any progress/interest in one year?

geowolf
Hi,
other projects are closing automatically any ticket that did not see any progress in one year.
Now, I believe that applied this blindly on bug reports, that's a no go and it's
offensive to reporters, but... I would suggest we do close improvement/new feature/task/wish tickets
that have not been updated in over one year.

That imho makes a good pair with the suggestion on our dashboard (https://osgeo-org.atlassian.net/projects/GEOS/summary)
not to open a new feature/improvement request unless it has been previously recourced.

The ticket can be closed with an explanation like:

"Closing all non bug report tickets that has seen no activity in one year. If you are interested in this ticket
we  encourage you to re-open it only after securing the necessary development resources. 
Please to read this guide to learn how to best deal with this type of requests."

What do you think?

Cheers
Andrea

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Reply | Threaded
Open this post in threaded view
|

Re: Mass close all improvement/new feature tickets that have not seen any progress/interest in one year?

Torben Barsballe
I agree, this seems like a good idea. I assume "Won't Fix" for the resolution? 
A quick manual pass-through of the closed tickets to ensure that no actual bugs that were misreported as new feature / improvement would probably be prudent.
While things are being mass-closed, we should probably also close all resolved tickets that haven't been updated in a year.

Do we want to officially document this somewhere as something that we will do every year?


Torben

On Thu, Nov 23, 2017 at 2:14 AM, Andrea Aime <[hidden email]> wrote:
Hi,
other projects are closing automatically any ticket that did not see any progress in one year.
Now, I believe that applied this blindly on bug reports, that's a no go and it's
offensive to reporters, but... I would suggest we do close improvement/new feature/task/wish tickets
that have not been updated in over one year.

That imho makes a good pair with the suggestion on our dashboard (https://osgeo-org.atlassian.net/projects/GEOS/summary)
not to open a new feature/improvement request unless it has been previously recourced.

The ticket can be closed with an explanation like:

"Closing all non bug report tickets that has seen no activity in one year. If you are interested in this ticket
we  encourage you to re-open it only after securing the necessary development resources. 
Please to read this guide to learn how to best deal with this type of requests."

What do you think?

Cheers
Andrea

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: <a href="tel:+39%200584%20962313" value="+390584962313" target="_blank">+39 0584 962313
fax: <a href="tel:+39%200584%20166%200272" value="+3905841660272" target="_blank">+39 0584 1660272
mob: <a href="tel:+39%20339%20884%204549" value="+393398844549" target="_blank">+39  339 8844549

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Reply | Threaded
Open this post in threaded view
|

Re: Mass close all improvement/new feature tickets that have not seen any progress/interest in one year?

geowolf
On Thu, Nov 23, 2017 at 6:56 PM, Torben Barsballe <[hidden email]> wrote:
I agree, this seems like a good idea. I assume "Won't Fix" for the resolution? 

I would go for "unresolved". "Wont' fix" might give the impression that we did not like the suggestion (I know, there is the explanation, but still)
 
A quick manual pass-through of the closed tickets to ensure that no actual bugs that were misreported as new feature / improvement would probably be prudent.

Agreed.
 
While things are being mass-closed, we should probably also close all resolved tickets that haven't been updated in a year.

Yeah, I have been doing that in the past every now and then.
 

Do we want to officially document this somewhere as something that we will do every year?

Hum... it could be part of the major release processes maybe? 
However those are hard enough by themselves, not sure if we want to add this as well

Cheers
Andrea

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Reply | Threaded
Open this post in threaded view
|

Re: Mass close all improvement/new feature tickets that have not seen any progress/interest in one year?

Torben Barsballe

Do we want to officially document this somewhere as something that we will do every year?

Hum... it could be part of the major release processes maybe? 
However those are hard enough by themselves, not sure if we want to add this as well

Agree that we probably don't want to add more to the major release process. And there isn't really anything else that is actually scheduled that has any sort of process tied to it (other than PMC meetings, which are also plenty busy).
I guess we can just leave this as a semi-impromptu thing that gets done every year or so then, and stick with the existing suggestion on our dashboard.

Torben

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Reply | Threaded
Open this post in threaded view
|

Re: Mass close all improvement/new feature tickets that have not seen any progress/interest in one year?

geowolf
Ok folks,
did a full run and updated tickets accordingly:
  • Most non "bug" reports were closed with a message asking people to consider resourcing the request and then eventually re-open the ticket
  • A few have been switched to bug
  • In other cases where the original reported was a developer I asked if there was intention to work on it in the short term, or please close
  • Found very few ones with a patch attached, I've marked them for "sprint" instead of closing to allow a dev to check them one last time and see if there is anything that can be salvaged before we close
Had to make a number of judgement calls and for sure I might have made mistakes processing one by one over 200 tickets... help welcomed to fix those! :-)

Cheers
Andrea


On Thu, Nov 23, 2017 at 7:38 PM, Torben Barsballe <[hidden email]> wrote:

Do we want to officially document this somewhere as something that we will do every year?

Hum... it could be part of the major release processes maybe? 
However those are hard enough by themselves, not sure if we want to add this as well

Agree that we probably don't want to add more to the major release process. And there isn't really anything else that is actually scheduled that has any sort of process tied to it (other than PMC meetings, which are also plenty busy).
I guess we can just leave this as a semi-impromptu thing that gets done every year or so then, and stick with the existing suggestion on our dashboard.

Torben



--

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility  for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Reply | Threaded
Open this post in threaded view
|

Re: Mass close all improvement/new feature tickets that have not seen any progress/interest in one year?

Ben Caradoc-Davies-2
Thanks for cleaning up, Andrea. Much appreciated!

Kind regards,
Ben.

On 11/12/17 03:10, Andrea Aime wrote:

> Ok folks,
> did a full run and updated tickets accordingly:
>
>     - Most non "bug" reports were closed with a message asking people to
>     consider resourcing the request and then eventually re-open the ticket
>     - A few have been switched to bug
>     - In other cases where the original reported was a developer I asked if
>     there was intention to work on it in the short term, or please close
>     - Found very few ones with a patch attached, I've marked them for
>     "sprint" instead of closing to allow a dev to check them one last time and
>     see if there is anything that can be salvaged before we close
>
> Had to make a number of judgement calls and for sure I might have made
> mistakes processing one by one over 200 tickets... help welcomed to fix
> those! :-)
>
> Cheers
> Andrea
>
>
> On Thu, Nov 23, 2017 at 7:38 PM, Torben Barsballe <
> [hidden email]> wrote:
>
>>
>>>> Do we want to officially document this somewhere as something that we
>>>> will do every year?
>>>>
>>>
>>> Hum... it could be part of the major release processes maybe?
>>> However those are hard enough by themselves, not sure if we want to add
>>> this as well
>>>
>>> Agree that we probably don't want to add more to the major release
>> process. And there isn't really anything else that is actually scheduled
>> that has any sort of process tied to it (other than PMC meetings, which are
>> also plenty busy).
>> I guess we can just leave this as a semi-impromptu thing that gets done
>> every year or so then, and stick with the existing suggestion on our
>> dashboard.
>>
>> Torben
>>
>
>
>
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
>
> _______________________________________________
> Geoserver-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

--
Ben Caradoc-Davies <[hidden email]>
Director
Transient Software Limited <https://transient.nz/>
New Zealand

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel