> If > there was a change and release, wouldn't it be better to preserve that > history and open an new albeit related JIRA?
Yes, please. Pulling the JIRA change log for 3.4.11 should reveal what features are included in 3.4.11. And, ideally, should document what, on sober second thought, is wrong with that feature. CAS-994 functions admirably for this purpose. Another JIRA issue should document the fix, change, improvement for some non-3.4.11 release. And by all means, link them, document that the one gave rise to the other. If this is a bug, then bonus points for setting the affects-version metadata on the new JIRA so that when someone queries the set of known issues in 3.4.11, they'll see this. Re-using a single JIRA issue for this misses a chance to clarify what changes happened for what CAS releases. My prior post was trimmed from the quoting here, but I think it was sensible: >>>> Bill, >>>> >>>> It looks like something was done for some version of CAS. "Did add >>>> timings that get logged per authentication handler". So, this JIRA issue >>>> should be updated to document the feature that was added for that release >>>> of CAS. >>>> >>>> Looks like Marvin then pointed out ways that the implementation could be >>>> better. That should be opened as a new improvement JIRA for wherever that >>>> improvement's going to be realized. 3.5, presumably. >>>> >>>> That sound sensible, and the way to use JIRA to communicate with adopters >>>> what's in the releases and capture the need for an improved >>>> implementation, track that to completion as well? >>>> >>>> Andrew Andrew On Jan 28, 2012, at 9:41 AM, William G. Thompson, Jr. wrote: > 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
