Hi,
just a quick note to inform you that I batch moved 250 issues to
closed states. These issues were in resolved states, and have not
been touched in the last month. This makes me think they are resolved
for good.
Cheers
Andrea
Cool.
I think it was due to the fact that I was using close, and some other people were using 'resolved' in the same way. So we should maybe standardize on 'close' when you finish an issue? I guess do 'resolved' if you want someone else to check on it?
Andrea Aime wrote:
Hi,
just a quick note to inform you that I batch moved 250 issues to
closed states. These issues were in resolved states, and have not
been touched in the last month. This makes me think they are resolved
for good.Cheers
Andrea-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Chris Holmes
The Open Planning Project
http://topp.openplans.org
Chris Holmes ha scritto:
Cool.
I think it was due to the fact that I was using close, and some other people were using 'resolved' in the same way. So we should maybe standardize on 'close' when you finish an issue? I guess do 'resolved' if you want someone else to check on it?
Yeah, that's the semantic I use usually, that is, I do resolve stuff hoping the user that created the issue will double check. But... I noticed that many times that user was me, so I would have better closed the issues straight away 
Cheers
Andrea