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 <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
