[Geoserver-devel] Next bug stomp date, and making it recurring

GeoServer GeoServer Developer
1

Hi all,
as discussed in the last meeting, we would like to propose April 28th as the
next bug fix code sprint.

Also, we’d like to make it recurring, “every last Friday of the month”, with
possible exceptions if there are holidays and the like (e.g, May 26th is
probably not the best day, it’s a long weekend in Italy)

Opinions/feedback/eager participants?

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.

2

+1

···

On 04/13/2017 02:06 PM, Andrea Aime wrote:

Hi all,
as discussed in the last meeting, we would like to propose April 28th as the
next bug fix code sprint.

Also, we’d like to make it recurring, “every last Friday of the month”, with
possible exceptions if there are holidays and the like (e.g, May 26th is
probably not the best day, it’s a long weekend in Italy)

Opinions/feedback/eager participants?

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](http://sdm.link/slashdot)

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)


-- 
==
GeoServer Professional Services from the experts! 
Visit [http://goo.gl/it488V](http://goo.gl/it488V) for more information.
==
Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy

phone: +39 0584 962313
fax:   +39 0584 1660272
mob:   +39  333 8128928

[http://www.geo-solutions.it](http://www.geo-solutions.it)
[http://twitter.com/geosolutions_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.
3

+1 for 28 April.

+1 to recur on the last Friday of every month, but discussion helps promote it and we can be flexible to accommodate holidays.

Count me in as a non-eager possible participant. :expressionless:

Kind regards,
Ben.

On 14/04/17 01:06, Andrea Aime wrote:

Hi all,
as discussed in the last meeting, we would like to propose April 28th as the
next bug fix code sprint.

Also, we'd like to make it recurring, "every last Friday of the month", with
possible exceptions if there are holidays and the like (e.g, May 26th is
probably not the best day, it's a long weekend in Italy)

Opinions/feedback/eager participants?

Cheers
Andrea

------------------------------------------------------------------------------
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
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

4

+1, thanks for chasing this onto the email list ben.

I think we could make a blog post for this month, and send out shorter monthly reminders linking to the blog post.

Matt made up some notes on the prep he needed to do to take part (mostly linking to developers guide). Perhaps we could turn it into a useful blog post.

···

On 13 April 2017 at 06:06, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi all,
as discussed in the last meeting, we would like to propose April 28th as the
next bug fix code sprint.

Also, we’d like to make it recurring, “every last Friday of the month”, with
possible exceptions if there are holidays and the like (e.g, May 26th is
probably not the best day, it’s a long weekend in Italy)

Opinions/feedback/eager participants?

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
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Jody Garnett

5

Jody,

thanks for the bug stomp blog post:
http://blog.geoserver.org/2017/04/27/geoserver-monthly-bug-stomp/

I have adjusted the Triage custom field settings so that it will be shown in the Default, Details, and View screens if not empty. Triage can now be set when editing; it will appear below Priority. Triage appears below Labels when viewing (this does not seem to be configurable). Please let me know if you would these settings changed.

Kind regards,
Ben.

On 15/04/17 05:52, Jody Garnett wrote:

I think we could make a blog post for this month, and send out shorter
monthly reminders linking to the blog post.

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

6

Triage was hidden so that non developers could not touch it and raise the attention on tickets they care for, is that still the case?
Also, I have had complaints about tickets marked for sprint that have not been addressed in several sprints, asvreported by user smart enough to notice the change history, again, it is sort of miscommunication the intention…

The original idea of the flag was to mark something as suitable for the sprint, e.g., in need of evaluation or supposedly easy to fix, but I am afraid the current marked tickets lost those qualities?

Cheers
Andrea

···

Il 28 Apr 2017 00:42, “Ben Caradoc-Davies” <ben@anonymised.com> ha scritto:

Jody,

thanks for the bug stomp blog post:
http://blog.geoserver.org/2017/04/27/geoserver-monthly-bug-stomp/

I have adjusted the Triage custom field settings so that it will be shown in the Default, Details, and View screens if not empty. Triage can now be set when editing; it will appear below Priority. Triage appears below Labels when viewing (this does not seem to be configurable). Please let me know if you would these settings changed.

Kind regards,
Ben.

On 15/04/17 05:52, Jody Garnett wrote:

I think we could make a blog post for this month, and send out shorter
monthly reminders linking to the blog post.

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

7

Anyone who can edit tickets can edit the Triage field.

With the previous settings, I found it hard to see if an issue was triaged for sprint, and saw no way to edit this status (unless it was Open or Reopened?). I seldom saw the Evaluate button when I wanted it.

- What if an issue is In Progress but in need of further work that could be part of a sprint?

- What if I completed an issue as part of a sprint, but it did not have Triage=sprint? How do I retrospectively triage it so it appears in the post-sprint report?

- What if an issue has Triage=sprint and should not? If it is hidden, I will never notice and will not fix it.

Kind regards,
Ben.

On 28/04/17 13:28, Andrea Aime wrote:

Triage was hidden so that non developers could not touch it and raise the
attention on tickets they care for, is that still the case?
Also, I have had complaints about tickets marked for sprint that have not
been addressed in several sprints, asvreported by user smart enough to
notice the change history, again, it is sort of miscommunication the
intention....

The original idea of the flag was to mark something as suitable for the
sprint, e.g., in need of evaluation or supposedly easy to fix, but I am
afraid the current marked tickets lost those qualities?

Cheers
Andrea

Il 28 Apr 2017 00:42, "Ben Caradoc-Davies" <ben@anonymised.com> ha scritto:

Jody,

thanks for the bug stomp blog post:
http://blog.geoserver.org/2017/04/27/geoserver-monthly-bug-stomp/

I have adjusted the Triage custom field settings so that it will be shown
in the Default, Details, and View screens if not empty. Triage can now be
set when editing; it will appear below Priority. Triage appears below
Labels when viewing (this does not seem to be configurable). Please let me
know if you would these settings changed.

Kind regards,
Ben.

On 15/04/17 05:52, Jody Garnett wrote:

I think we could make a blog post for this month, and send out shorter
monthly reminders linking to the blog post.

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

8

Hi Ben,
I am reviewing tickets and see users have started filling triage with improbable values (which is probably
not as bad as them marking the ticket for sprint, but still bad).

In the current setup the field has probably lost the intended usage, should we get rid of it and find something
that the users cannot touch?

Cheers
Andrea

···

On Fri, Apr 28, 2017 at 4:50 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Anyone who can edit tickets can edit the Triage field.

With the previous settings, I found it hard to see if an issue was triaged for sprint, and saw no way to edit this status (unless it was Open or Reopened?). I seldom saw the Evaluate button when I wanted it.

  • What if an issue is In Progress but in need of further work that could be part of a sprint?

  • What if I completed an issue as part of a sprint, but it did not have Triage=sprint? How do I retrospectively triage it so it appears in the post-sprint report?

  • What if an issue has Triage=sprint and should not? If it is hidden, I will never notice and will not fix it.

Kind regards,
Ben.

On 28/04/17 13:28, Andrea Aime wrote:

Triage was hidden so that non developers could not touch it and raise the
attention on tickets they care for, is that still the case?
Also, I have had complaints about tickets marked for sprint that have not
been addressed in several sprints, asvreported by user smart enough to
notice the change history, again, it is sort of miscommunication the
intention…

The original idea of the flag was to mark something as suitable for the
sprint, e.g., in need of evaluation or supposedly easy to fix, but I am
afraid the current marked tickets lost those qualities?

Cheers
Andrea

Il 28 Apr 2017 00:42, “Ben Caradoc-Davies” <ben@anonymised.com> ha scritto:

Jody,

thanks for the bug stomp blog post:
http://blog.geoserver.org/2017/04/27/geoserver-monthly-bug-stomp/

I have adjusted the Triage custom field settings so that it will be shown
in the Default, Details, and View screens if not empty. Triage can now be
set when editing; it will appear below Priority. Triage appears below
Labels when viewing (this does not seem to be configurable). Please let me
know if you would these settings changed.

Kind regards,
Ben.

On 15/04/17 05:52, Jody Garnett wrote:

I think we could make a blog post for this month, and send out shorter
monthly reminders linking to the blog post.

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

–
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

–

==
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.

9

On Sat, May 13, 2017 at 4:28 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

In the current setup the field has probably lost the intended usage,
should we get rid of it and find something
that the users cannot touch?

Mind, let's not drop it before we find a way to mark sprint tickets without
any random user being able to do the same,
and migrate if necessary.

Ben, what was the original problem you wanted to solve by allowing
visibility of the field?

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.

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

10

Andrea,

I am guessing that this garbage input is mostly happening on the creation screen. I will see if I can remove it. We could also lock the values if we can. What should be permitted? "sprint" and "geogig"(?) I think these were the original values.

Kind regards,
Ben.

On 14/05/17 02:28, Andrea Aime wrote:

Hi Ben,
I am reviewing tickets and see users have started filling triage with
improbable values (which is probably
not as bad as them marking the ticket for sprint, but still bad).

In the current setup the field has probably lost the intended usage, should
we get rid of it and find something
that the users cannot touch?

Cheers
Andrea

On Fri, Apr 28, 2017 at 4:50 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Anyone who can edit tickets can edit the Triage field.

With the previous settings, I found it hard to see if an issue was triaged
for sprint, and saw no way to edit this status (unless it was Open or
Reopened?). I seldom saw the Evaluate button when I wanted it.

- What if an issue is In Progress but in need of further work that could
be part of a sprint?

- What if I completed an issue as part of a sprint, but it did not have
Triage=sprint? How do I retrospectively triage it so it appears in the
post-sprint report?

- What if an issue has Triage=sprint and should not? If it is hidden, I
will never notice and will not fix it.

Kind regards,
Ben.

On 28/04/17 13:28, Andrea Aime wrote:

Triage was hidden so that non developers could not touch it and raise the
attention on tickets they care for, is that still the case?
Also, I have had complaints about tickets marked for sprint that have not
been addressed in several sprints, asvreported by user smart enough to
notice the change history, again, it is sort of miscommunication the
intention....

The original idea of the flag was to mark something as suitable for the
sprint, e.g., in need of evaluation or supposedly easy to fix, but I am
afraid the current marked tickets lost those qualities?

Cheers
Andrea

Il 28 Apr 2017 00:42, "Ben Caradoc-Davies" <ben@anonymised.com> ha scritto:

Jody,

thanks for the bug stomp blog post:
http://blog.geoserver.org/2017/04/27/geoserver-monthly-bug-stomp/

I have adjusted the Triage custom field settings so that it will be shown
in the Default, Details, and View screens if not empty. Triage can now be
set when editing; it will appear below Priority. Triage appears below
Labels when viewing (this does not seem to be configurable). Please let
me
know if you would these settings changed.

Kind regards,
Ben.

On 15/04/17 05:52, Jody Garnett wrote:

I think we could make a blog post for this month, and send out shorter

monthly reminders linking to the blog post.

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

11

On 14/05/17 02:45, Andrea Aime wrote:

Ben, what was the original problem you wanted to solve by allowing
visibility of the field?

To be able to see and edit the Triage field so I could notice and remove sprint tickets that should not be, or add sprint tickets that are already in progress.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

12

Andrea,

because we use the View screen for both creation and view, I do not see that Triage can be removed from the creation screen without also removing it from the ordinary view (unless the scheme is refactored). I changed the description to *Leave the Triage field empty unless you have a good reason.* (bold). I hope this helps reduce unwanted entries. If it continues to cause problems, we can remove it from the View screen.

If we replace this field with something else, we could consider a checkbox, which might be less likely to attract garbage values.

Kind regards,
Ben.

On 14/05/17 09:46, Ben Caradoc-Davies wrote:

Andrea,

I am guessing that this garbage input is mostly happening on the
creation screen. I will see if I can remove it. We could also lock the
values if we can. What should be permitted? "sprint" and "geogig"(?) I
think these were the original values.

Kind regards,
Ben.

On 14/05/17 02:28, Andrea Aime wrote:

Hi Ben,
I am reviewing tickets and see users have started filling triage with
improbable values (which is probably
not as bad as them marking the ticket for sprint, but still bad).

In the current setup the field has probably lost the intended usage,
should
we get rid of it and find something
that the users cannot touch?

Cheers
Andrea

On Fri, Apr 28, 2017 at 4:50 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Anyone who can edit tickets can edit the Triage field.

With the previous settings, I found it hard to see if an issue was
triaged
for sprint, and saw no way to edit this status (unless it was Open or
Reopened?). I seldom saw the Evaluate button when I wanted it.

- What if an issue is In Progress but in need of further work that could
be part of a sprint?

- What if I completed an issue as part of a sprint, but it did not have
Triage=sprint? How do I retrospectively triage it so it appears in the
post-sprint report?

- What if an issue has Triage=sprint and should not? If it is hidden, I
will never notice and will not fix it.

Kind regards,
Ben.

On 28/04/17 13:28, Andrea Aime wrote:

Triage was hidden so that non developers could not touch it and
raise the
attention on tickets they care for, is that still the case?
Also, I have had complaints about tickets marked for sprint that
have not
been addressed in several sprints, asvreported by user smart enough to
notice the change history, again, it is sort of miscommunication the
intention....

The original idea of the flag was to mark something as suitable for the
sprint, e.g., in need of evaluation or supposedly easy to fix, but
I am
afraid the current marked tickets lost those qualities?

Cheers
Andrea

Il 28 Apr 2017 00:42, "Ben Caradoc-Davies" <ben@anonymised.com> ha
scritto:

Jody,

thanks for the bug stomp blog post:
http://blog.geoserver.org/2017/04/27/geoserver-monthly-bug-stomp/

I have adjusted the Triage custom field settings so that it will be
shown
in the Default, Details, and View screens if not empty. Triage can
now be
set when editing; it will appear below Priority. Triage appears below
Labels when viewing (this does not seem to be configurable). Please
let
me
know if you would these settings changed.

Kind regards,
Ben.

On 15/04/17 05:52, Jody Garnett wrote:

I think we could make a blog post for this month, and send out shorter

monthly reminders linking to the blog post.

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

13

On Sat, May 13, 2017 at 11:49 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

On 14/05/17 02:45, Andrea Aime wrote:

Ben, what was the original problem you wanted to solve by allowing
visibility of the field?

To be able to see and edit the Triage field so I could notice and remove
sprint tickets that should not be, or add sprint tickets that are already
in progress.

That should have been doable already without any changes, as far as I know,
but was restricted to developers:

   - To edit the triage field, use the "evaluate" button at the end of the
   top menu/button master
   - To view tickets considered potential targets for the sprint, there is
   a public saved search,
   https://osgeo-org.atlassian.net/issues/?filter=11300

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.

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

14

On 14/05/17 22:09, Andrea Aime wrote:

On Sat, May 13, 2017 at 11:49 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

On 14/05/17 02:45, Andrea Aime wrote:

Ben, what was the original problem you wanted to solve by allowing
visibility of the field?

To be able to see and edit the Triage field so I could notice and remove
sprint tickets that should not be, or add sprint tickets that are already
in progress.

That should have been doable already without any changes, as far as I know,
but was restricted to developers:
   - To edit the triage field, use the "evaluate" button at the end of the
   top menu/button master
   - To view tickets considered potential targets for the sprint, there is
   a public saved search,
   https://osgeo-org.atlassian.net/issues/?filter=11300

This still does not display the Triage field when viewing an issue, nor does it allow its modification for issues not in Open or Reopened state because the Evaluate transition applies only to these states. These are the things I was trying to change. Please let me know if my changes continue to cause problems; I am happy to revert.

The saved filter should also include Reopened issues.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

15

On Sun, May 14, 2017 at 11:11 PM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

This still does not display the Triage field when viewing an issu

That was by design, normal users should not see the field, it might give
the wrong impression that a ticket will
be solved when it's just marked for "getting a look".

nor does it allow its modification for issues not in Open or Reopened
state because the Evaluate transition applies only to these states.

Err... why do you need to change it for a closed issue? Can the workflow be
modified so that an issue in resolved
state can be evaluated? A closed one should really be not touched.

These are the things I was trying to change. Please let me know if my
changes continue to cause problems; I am happy to revert.

The saved filter should also include Reopened issues.

Good catch! Done.

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.

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

16

On 16/05/17 02:32, Andrea Aime wrote:

That was by design, normal users should not see the field, it might give
the wrong impression that a ticket will
be solved when it's just marked for "getting a look".

I see your point. "sprint" might be taken as a priority, when it actually denotes a charity case that might be fixable with a small unfunded effort.

The problem is that the Triage state cannot be seen. Do I have to put an issue back into Open and then hit Evaluate to even see if it has Triage "sprint"?

Perhaps a new field with less suggestive name? "stompable"?

Err... why do you need to change it for a closed issue? Can the workflow be
modified so that an issue in resolved
state can be evaluated? A closed one should really be not touched.

I was thinking more of an In Progress issue. Why should the state be changed to just to see or modify a field?

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

17

On Tue, May 16, 2017 at 1:18 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

On 16/05/17 02:32, Andrea Aime wrote:

That was by design, normal users should not see the field, it might give
the wrong impression that a ticket will
be solved when it's just marked for "getting a look".

I see your point. "sprint" might be taken as a priority, when it actually
denotes a charity case that might be fixable with a small unfunded effort.

The problem is that the Triage state cannot be seen. Do I have to put an
issue back into Open and then hit Evaluate to even see if it has Triage
"sprint"?

Perhaps a new field with less suggestive name? "stompable"?

I am not sure, Jody set this up, I was hoping him to join the
conversation...
Generally speaking I don't believe we necessarily need to have that field
visible, you can find the issues marked for
sprint with the search, or click evaluate to see the field (minus the in
progress bit below).

Err... why do you need to change it for a closed issue? Can the workflow be

modified so that an issue in resolved
state can be evaluated? A closed one should really be not touched.

I was thinking more of an In Progress issue. Why should the state be
changed to just to see or modify a field?

Again, Jody knows the answer here, but I hope the "evaluate" button can
also be added to "in progress" tickets.

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.

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

18

State change was used to because field visibility can be customized for those state changes.

I am happy to change the name to “reserved”, or “funded” or “volunteer”; still all of those (if visible outside of the state change trick) would discourage volunteers or funding for issues marked such.

The real point here Ben with the hidden field is to prevent the terrible spreadsheet we had perviously.

I would also like to mark “sprint” bugs that have taken up one day, and given them a suitable label like “difficult”.

···

–
Jody Garnett

On 16 May 2017 at 06:57, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Tue, May 16, 2017 at 1:18 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

On 16/05/17 02:32, Andrea Aime wrote:

That was by design, normal users should not see the field, it might give
the wrong impression that a ticket will
be solved when it’s just marked for “getting a look”.

I see your point. “sprint” might be taken as a priority, when it actually denotes a charity case that might be fixable with a small unfunded effort.

The problem is that the Triage state cannot be seen. Do I have to put an issue back into Open and then hit Evaluate to even see if it has Triage “sprint”?

Perhaps a new field with less suggestive name? “stompable”?

I am not sure, Jody set this up, I was hoping him to join the conversation…
Generally speaking I don’t believe we necessarily need to have that field visible, you can find the issues marked for
sprint with the search, or click evaluate to see the field (minus the in progress bit below).

Err… why do you need to change it for a closed issue? Can the workflow be
modified so that an issue in resolved
state can be evaluated? A closed one should really be not touched.

I was thinking more of an In Progress issue. Why should the state be changed to just to see or modify a field?

Again, Jody knows the answer here, but I hope the “evaluate” button can also be added to “in progress” tickets.

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.

19

Thanks, Jody, the new system is a great improvement over the spreadsheet and much appreciated. A visible field that is less inviting to the uninformed might help; I do not like any of the suggestions so far (including mine).

Do you intend to use the "Labels" field for the "difficult" label? That makes sense to me.

Kind regards,
Ben.

On 17/05/17 18:41, Jody Garnett wrote:

State change was used to because field visibility can be customized for
those state changes.

I am happy to change the name to "reserved", or "funded" or "volunteer";
still all of those (if visible outside of the state change trick) would
discourage volunteers or funding for issues marked such.

The real point here Ben with the hidden field is to prevent the terrible
spreadsheet we had perviously.

I would also like to mark "sprint" bugs that have taken up one day, and
given them a suitable label like "difficult".

--
Jody Garnett

On 16 May 2017 at 06:57, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Tue, May 16, 2017 at 1:18 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

On 16/05/17 02:32, Andrea Aime wrote:

That was by design, normal users should not see the field, it might give
the wrong impression that a ticket will
be solved when it's just marked for "getting a look".

I see your point. "sprint" might be taken as a priority, when it actually
denotes a charity case that might be fixable with a small unfunded effort.

The problem is that the Triage state cannot be seen. Do I have to put an
issue back into Open and then hit Evaluate to even see if it has Triage
"sprint"?

Perhaps a new field with less suggestive name? "stompable"?

I am not sure, Jody set this up, I was hoping him to join the
conversation...
Generally speaking I don't believe we necessarily need to have that field
visible, you can find the issues marked for
sprint with the search, or click evaluate to see the field (minus the in
progress bit below).

Err... why do you need to change it for a closed issue? Can the workflow

be
modified so that an issue in resolved
state can be evaluated? A closed one should really be not touched.

I was thinking more of an In Progress issue. Why should the state be
changed to just to see or modify a field?

Again, Jody knows the answer here, but I hope the "evaluate" button can
also be added to "in progress" tickets.

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 <+39%200584%20962313>
fax: +39 0584 1660272 <+39%200584%20166%200272>
mob: +39 339 8844549 <+39%20339%20884%204549>

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.

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

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

20

On 16/05/17 02:32, Andrea Aime wrote:

The saved filter should also include Reopened issues.

Good catch! Done.

Please also sort by Created descending. The default sort is by Jira tag descending so all GeoTools issues are before all GeoServer issues. Or perhaps we should offer oldest issues first? Are we trying to stomp new issues quickly or clean out dusty ones in the attic?

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand