That seems fine (though I wonder if there is a better location/name for cas-4.0?).
Also, just a note that when we migrate cas 3.4.x, to be mindful of the extra directory. On Tue, Sep 6, 2011 at 9:08 AM, Marvin Addison <[email protected]>wrote: > I'd like to take the GitHub migration as an opportunity to drop old, > stale, or irrelevant branches from the repository. Pruning dead > branches will help increase clarity about what versions are actively > maintained. I propose the following branches be preserved and mapped > to new branches: > > 1. trunk -> cas-4.0 > 2. cas-3_4_x_maintenance -> master > 3. cas-3_3_x_maintenance -> cas-3.3-maint > 4. cas-3-2_maintenance -> cas-3.2-maint > > Note that the first two changes are part of > https://issues.jasig.org/browse/CAS-997. All other branches would be > deleted, including the LPPE branch and some older (presumably dead) > maintenance branches. Branches like LPPE and other experimental work > can be justifiably purged due to new workflows facilitated by git; for > example, simply clone the repo into a personal GitHub repo, work away, > then send a pull request upon fitness for merging with master. > > Let's simply vote on this proposal and hopefully any severe reaction > will shake out in the voting. Anyone may vote but only votes by > active devs count. > > 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
