On Wed, Jan 11, 2012 at 10:38 AM, Marvin Addison <marvin.addi...@gmail.com> wrote: >> 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.
+1 > I can own it for the interim, > but I'd love for someone else to volunteer for the effort. I'm happy to pick up 3.4.x branch maintenance once 3.5 is cut. Also happy to bring the current 3.4.x branch up to 3.4.11. Bill > > M > > -- > 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
