On Tue, Apr 3, 2012 at 6:56 PM, Scott Battaglia <scott.battag...@gmail.com> wrote: > Why would that have been deleted?
See http://groups.google.com/group/cas-dev/browse_thread/thread/4d6881af97c73f3d/87e56c5b4f110f81?lnk=gst&q=3.5+#87e56c5b4f110f81 Scott, you are absent from that thread, so perhaps you missed the discussion? A prospective 3.4.12 only came back on the table due to CAS-1071. Personally, I don't think it is worth the effort since there are workarounds for the issue and 3.5 is around the corner. Bill > > > > On Tue, Apr 3, 2012 at 6:11 PM, Marvin Addison <marvin.addi...@gmail.com> > wrote: >> >> > I had a number that I had originally marked as 3.4.12 that had actually >> > been >> > resolved for 3.4.12. Do we know if they are still marked as resolved >> > for >> > that? >> >> Doubtful, since I had to create a 3.4.12 version on the admin console >> prior to updating issues. I wonder if a Jira wizard could craft a >> query to search for issue changes to identify version number >> flip-flops. >> >> M >> >> -- >> You are currently subscribed to cas-dev@lists.jasig.org as: >> scott.battag...@gmail.com >> >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev >> > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: wgt...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
