> There are proposed items listed for 3.5 that are just > that...proposals. Please only put other proposals there if you intend > to work on them. This is not a wishlist of things you'd like someone > else to implement. That list is over here: > https://wiki.jasig.org/display/CAS/Wishlist
Overall I'd like to see more steps in between 3.5 and 4.0, which Scott had mapped out in the previous roadmap document. There are API changes that could likely be made stepwise instead of lump sum in 4.0. I've really come around to the wisdom of getting to 4 via evolutionary steps instead of a revolutionary new product with vastly different APIs from the previous production release. > I'd very much like some feedback on the overall form of the roadmap > and on how to proceed with the process of opening up 3.5 for active > development. Again, I'm interested in making any reasonable API changes that make sense for the product and features we want to ship. While I think a minor release makes sense for the next target version, I absolutely do not want to get bogged down in what to call this release. If there are good API changes to be made and the scope is beyond a minor release, simply call it 4.0. That said, once we agree on the roadmap the version numbers should be set in stone. I'd really like to see more items from Scott's roadmap on there. Monitoring and management capabilities (e.g. via JMX) come to mind as a good candidate for this release since they add value without costing dramatic API changes. M -- 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
