Is was unclear to me if there was a change applied and released already. The meta data says fix for 3.4.11 which was already cut. If there was a change and release, wouldn't it be better to preserve that history and open an new albeit related JIRA?
In any case, Marvin, since you're stepping up to it, why don't you do what's most appropriate. My main objective was to fix up JIRA for the already released 3.4.11...which has this unresolved issue handing out there. Best, Bill On Sat, Jan 28, 2012 at 7:18 AM, Marvin Addison <[email protected]> wrote: >> So close this one, and open another then? > > Seems to me we should simply track a fix on the same issue. This is > pretty SOP in my experience: a problem is discovered with a fix to an > issue so it's reopened until the problem is resolved. Just assign to > me and I'll provide a patch via pull. I believe it will be > straightforward to allow the sort of configuration needed to log the > performance stats to log4j logger, with all of its configuration > flexibility. That is to say it would be consistent with a point > release. > > M > > -- > You are currently subscribed to [email protected] as: [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
