To add a new feature or fix a bug using a github pull request, should a JIRA ticket be created first? The documentation (http://docs.geoserver.org/latest/en/developer/policies/patches.html#github-pull-requests) does not mention creating a ticket for this case.
Thanks,
Michael
Hi Micheal,
I dont think we have a set policy on this but i think github pull request are fine. However for larger scale changes we have the gsip process which describes via proposal a change a developer wishes to make and goes through a formal voting process. So depending on the change you might be asked for more.
That said it never hurts to create a supplementary jira issue for a change. One benefit of which is that it shows up in the official change log (release notes) for a release. Although as we get more contributions via pull request we will probably want to start including them in the release notes.
Anyways like I said this is not official but just my thoughts after a month or so of being on git hub. I am sure other devs will have opinions as well.
-Justin
On Friday, August 3, 2012, Michael Romero wrote:
To add a new feature or fix a bug using a github pull request, should a
JIRA ticket be created first? The documentation
(http://docs.geoserver.org/latest/en/developer/policies/patches.html#github-pull-requests)
does not mention creating a ticket for this case.
Thanks,
Michael
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
That’s kind of what I thought. I will create JIRA tickets too until the pull requests are included in the release notes. Thanks Justin.
Michael
···
On 08/06/2012 11:25 AM, Justin Deoliveira wrote:
Hi Micheal,
I dont think we have a set policy on this but i think github pull request are fine. However for larger scale changes we have the gsip process which describes via proposal a change a developer wishes to make and goes through a formal voting process. So depending on the change you might be asked for more.
That said it never hurts to create a supplementary jira issue for a change. One benefit of which is that it shows up in the official change log (release notes) for a release. Although as we get more contributions via pull request we will probably want to start including them in the release notes.
Anyways like I said this is not official but just my thoughts after a month or so of being on git hub. I am sure other devs will have opinions as well.
-Justin
On Friday, August 3, 2012, Michael Romero wrote:
To add a new feature or fix a bug using a github pull request, should a
JIRA ticket be created first? The documentation
(http://docs.geoserver.org/latest/en/developer/policies/patches.html#github-pull-requests)
does not mention creating a ticket for this case.
Thanks,
Michael
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.