I was suggesting that we might have a branch that is "current release" at all times and updated with the code of the current release on each release. The point is to have a place where deployers, not developers, could always fork their customizations from if they wanted to store their maven overlay in GITHub.
-Andrew On Oct 3, 2011, at 5:39 PM, Andrew Petro wrote: > Andrew, > > This branch should be marching towards the next 3.4.x release. > > https://github.com/Jasig/cas/tree/3.4.x > > Master is currently marching towards 3.5.0. > > Andrew > > > > On 10/03/2011 02:09 PM, Tillinghast, Andrew P. wrote: >> Is there a branch of the Git Repo that contains the code of the current >> release? >> >> It would be nice to have a branch that deployers could fork to maintain >> their maven customizations where they could just merge to get the latest >> release. >> >> I was expecting master to hold the release and the branches the work in >> progress but based on the commit dates I don't think that's the case. >> >> >> -Andrew >> >> > > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: > atill...@conncoll.edu > 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
