Justin Deoliveira ha scritto: >> As an instance, let's say I am looking at the code and I find a place >> where I can make a minor improvement, by, let's say, adding generics, >> changing a cycle order to make it faster, adding a few more check to >> improve robustness: in principle I should create jira before each of >> these steps, which is IMHO more a waste of time than a useful thing >> since it likes raise the bar for doing maintenance clean up, which is >> the kind of work what you do when you are "playing" with the codebase. > Not sure where this is coming from. Never did the process mandate that > jira be made for these types of changes, although i don't see it as a > bad idea though, every change having a jira makes that change trackable > which imo is just good practice.
Agreed, trackable jiras are good for at least a couple of reasons: - changelog - a jira can contain a discussion on to why a change was made, which is always good context one year later when you wonder why a change was made and what could break if one fiddles again with the code That said, for really minor changes I don't think a jira provides any benefit, and I don't remember we ever mandated one for real small things either. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
