Okay, no arguments on keeping it in there, just possibly a name that facilitates its purpose (cas_api_design_experiments or some such thing?) that makes it clear we test our API changes there before merging back into the master?
Thanks for taking the lead on getting this done. Cheers, Scott On Tue, Sep 6, 2011 at 9:41 AM, Marvin Addison <[email protected]>wrote: > > That seems fine (though I wonder if there is a better location/name for > > cas-4.0?). > > There's a lot of benefit to keeping the next generation part of the > same repository; for example, it facilitates merging features into > master. :) I'm totally open to alternative naming since we have no > idea of the exact version number where it will be released. The good > thing is that branch names are much more mutable with git so we can > change at the drop of a hat. > > > Also, just a note that when we migrate cas 3.4.x, to be mindful of the > extra > > directory. > > Got it. I've staged this thing like 10 times and it looks good > afaict. Branch cleanup is the last TODO item before we set a time for > transition. > > 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 > -- 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
