> I see that CAS 3.4.11 [1] includes fixes not present in the 3.4.x > maintenance branch [2].
I don't think we have become used to the process needed to merge commits to master into maintenance branches. I've done a few in the past, but I haven't done any recently and I can imagine it's quite stale. (Other devs may have done some as well -- haven't looked carefully.) I'll take an action item to get it current, but someone needs to take lead on each maintenance branch. In fact I'd say that's the litmus test for creating maintenance versions -- an active maintainer to do menial work like this. I can own it for the interim, but I'd love for someone else to volunteer for the effort. 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
