Hi,
in the last few days I've seen patches checked inside GeoServer source
code without any reference to a Jira issue.
This is bad, it means we don't have anything to track the change,
the change won't be included in the release changelog, and only people
subscribed to the commits mailing list (like me) will notice them.
Pretty please, can you open (and close) a jira issue and refer
to it when you commit?
Cheers
Andrea
Whoopsy :). My patch was a foward port from 1.6.x...i dug up the jira for it and marked it fixed for 1.6.0-rc1.
-Justin
Andrea Aime wrote:
Hi,
in the last few days I've seen patches checked inside GeoServer source
code without any reference to a Jira issue.
This is bad, it means we don't have anything to track the change,
the change won't be included in the release changelog, and only people
subscribed to the commits mailing list (like me) will notice them.Pretty please, can you open (and close) a jira issue and refer
to it when you commit?Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel!DSPAM:4007,469f20ad201886491211187!
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Note also that if you reference the jira issue, like GEOS-932, then the commit message will create a nice hyperlink to that issue automatically, they must have set up something to auto resolve such things on codehaus.
Justin Deoliveira wrote:
Whoopsy :). My patch was a foward port from 1.6.x...i dug up the jira for it and marked it fixed for 1.6.0-rc1.
-Justin
Andrea Aime wrote:
Hi,
in the last few days I've seen patches checked inside GeoServer source
code without any reference to a Jira issue.
This is bad, it means we don't have anything to track the change,
the change won't be included in the release changelog, and only people
subscribed to the commits mailing list (like me) will notice them.Pretty please, can you open (and close) a jira issue and refer
to it when you commit?Cheers
Andrea-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel