[Geoserver-devel] JIRA workflow doubts

GeoServer GeoServer Developer
1

Hi,

I have a doubt regarding geoserver JIRA issues.

Consider this use case, I want to implement a new feature or fix a bug,
so I create an issue for that and do a pull request that is merged on master.

After some time (and community acceptance) I decide to backport it.
What should be done regarding JIRA ?

Update the original issue (but at that time she was probably closed)?
Create a new issue for the backporting ? If yes with which type task,
improvement or new feature ?

The commit should stay associated to the original issues right ?

I know some of this stuff is implicit in the developer guide:
http://docs.geoserver.org/stable/en/developer/

but for a new comer (at least to me) is not always evident how JIRA
issues should be managed and what is their impact on the project management.

I think that the developer guide could benefit from having a section
about JIRA issues in the context of GeoServer.

Regards,

Nuno Oliveira

--

GeoServer Professional Services from the experts!
Visit 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://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

Nuno,

I recommend using the original Jira issue and adding a new Fix Version for the next release on the backport branch. You should be able to do this even for Closed issues. When the next release is made on the backport branch, the issue will then be included in the Jira changelog.

I often use the original Jira title as the git commit title, using Andrea's trick of Export / XML to get a nicely formatted title.

Git records what you changed; Jira lets you record why you changed it. For backports, the "why" is the same, so use the same Jira issue.

Kind regards,
Ben.

On 19/07/16 23:24, Nuno Oliveira wrote:

Hi,

I have a doubt regarding geoserver JIRA issues.

Consider this use case, I want to implement a new feature or fix a bug,
so I create an issue for that and do a pull request that is merged on master.

After some time (and community acceptance) I decide to backport it.
What should be done regarding JIRA ?

Update the original issue (but at that time she was probably closed)?
Create a new issue for the backporting ? If yes with which type task,
improvement or new feature ?

The commit should stay associated to the original issues right ?

I know some of this stuff is implicit in the developer guide:
http://docs.geoserver.org/stable/en/developer/

but for a new comer (at least to me) is not always evident how JIRA
issues should be managed and what is their impact on the project management.

I think that the developer guide could benefit from having a section
about JIRA issues in the context of GeoServer.

Regards,

Nuno Oliveira

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

3

When the next release is made on the backport branch, the issue will then be included in the Jira changelog.

This answer my doubts, I will follow your recommendations.

Thanks for the feedback Ben.

Le mardi 19 juillet 2016 à 23:44 +1200, Ben Caradoc-Davies a écrit :

Nuno,

I recommend using the original Jira issue and adding a new Fix Version
for the next release on the backport branch. You should be able to do
this even for Closed issues. When the next release is made on the
backport branch, the issue will then be included in the Jira changelog.

I often use the original Jira title as the git commit title, using
Andrea's trick of Export / XML to get a nicely formatted title.

Git records what you changed; Jira lets you record why you changed it.
For backports, the "why" is the same, so use the same Jira issue.

Kind regards,
Ben.

On 19/07/16 23:24, Nuno Oliveira wrote:
> Hi,
>
> I have a doubt regarding geoserver JIRA issues.
>
> Consider this use case, I want to implement a new feature or fix a bug,
> so I create an issue for that and do a pull request that is merged on master.
>
> After some time (and community acceptance) I decide to backport it.
> What should be done regarding JIRA ?
>
> Update the original issue (but at that time she was probably closed)?
> Create a new issue for the backporting ? If yes with which type task,
> improvement or new feature ?
>
> The commit should stay associated to the original issues right ?
>
> I know some of this stuff is implicit in the developer guide:
> http://docs.geoserver.org/stable/en/developer/
>
> but for a new comer (at least to me) is not always evident how JIRA
> issues should be managed and what is their impact on the project management.
>
> I think that the developer guide could benefit from having a section
> about JIRA issues in the context of GeoServer.
>
> Regards,
>
> Nuno Oliveira
>

--

GeoServer Professional Services from the experts!
Visit 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://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.