I have just merged the latest set of changes on ldaptive and principal resolvers. I believe the branch on that end is also feature-complete now. Process-wise, I'd like to propose that we bring the branch up to speed with master, go through a few rounds of cleanup and make sure the code style is compatible with our conventions by checkstyle. We should next be able to do one wholesome review and finally bring the changes into master.
Other suggestions are most welcome. > -----Original Message----- > From: Marvin S. Addison [mailto:[email protected]] > Sent: Thursday, June 06, 2013 6:32 AM > To: [email protected] > Subject: [cas-dev] Authn API Status > > I just issued a pull onto the feature-new-authn-api branch for some > credential cleanup, and I'd like to do another subsequent one for the > CredentialsToPrincipalResolver. There isn't a whole lot of functional change > in either one, but they are valuable in my mind. In any case I think we're > functionally complete on that branch at present and are ready to merge into > master at any suitable time. There is some additional work to remove old code > and possibly additional work on LPPE refactoring, but both could be > accomplished after RC1 if needed. Are there any substantial objections to > merging this branch into master by Monday at the latest? We could then do > some final cleanup and sanity testing before cutting the RC later in the > week. Note that we would be slipping from the intended Monday, June 10 RC1 > date with that approach, but I'm inclined to wait a couple of days for a more > polished product. > > Thanks, > 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
