Merge my work into master immediately following 3.5 release so it goes into
the next release, whatever its name and timeline, and refactor the LPPE work
to accommodate the API changes.
The above compromise respects my desire to move forward with API changes
that support present (password expiration for other authentication methods)
and future (multifactor auth) use cases. It respects your desire to keep
momentum toward 3.5 and its goals of small to moderate changes.
Works for me. I'll plan on executing on the plan early next week.
Sounds good. In the interim I'll update the RoadMap to reflect this
strategy. I'm also eager to document other features for the next
release including work on storage APIs. There are some pressing matters
to address (JPA and serialization generally) that can be resolved neatly
through some refactoring of the storage APIs. I'll attempt to discuss
them at a high level on the roadmap, then solicit feedback here.
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
