Hey folks,
As I wrap up the 2.2-beta2 release i am looking at the changelog for
2.2-beta2 and something is a miss.
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10311&version=18437
Just over a dozen issues... doesn't sound right and indeed it is not.
What's happening is that issues resolved are not being marked with a
fixVersion or marked with a fixVersion on 2.1.x only even though the fix
occurs on trunk as well.
First question. Is this intentional? If the answer is no second question is
can we make it jira policy to (a) always mark the fixVersion and (b) mark
it to reflect all branches a fix was done on?
Thanks.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
