On Tue, Aug 30, 2011 at 12:54 PM, Marvin Addison <[email protected]> wrote: >> 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.
Based on the release strategy any given improvement could be considered for the 3.x line (as long as there is developer interested in working on it). Where it fits, point or minor, depends on how it squares with the release strategy. I too adhere to the wisdom that it is better to bring in improvements to the current shipping code base sooner rather than later. I'm trying to steer away from top-down planning towards a more practical near-term bottom-up approach consistent with a Jasig style of development. If anyone is interested in working on any of those items that were previous mapped out, they should be considered for 3.5 if they square with the release strategy. Items that have no developer interest have to wait on the wishlist. The roadmap is just a starting point. Individual developers interested in committing to work should fill it out and bring discussion about intent and approach to the cas-dev list. I didn't intend to have the roadmap imply that 3.5 is necessarily a step towards CAS4 or the last 3.x release nor that CAS4 necessarily comes after 3.5. CAS4 could, given the release strategy, be released ahead of, after, or simultaneously with 3.5. The gating factor for any release or improvement is folks interested in working on them. >> 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. One way for us not to get bogged down on what to call a release is for us to instead agree on the release strategy and let that drive the roadmap and the release versioning. The four proposal on the list so far appear to be consistent with a minor release, and that would imply a 3.5. The work that has been done in trunk towards a redesign of CAS is consistent with a major release, thus 4.0. Practically, if there is work being down on a minor release, then by definition it encompasses any work that would be proposed for a point release. In others words, if 3.5 takes flight, it would be unlikely another 3.4.x would also at the same time, unless there is a compelling reason and developer interest. > > 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. Totally in agreement here. The question is, who is going to commit to working on those items, as that is how they move from the wishlist to the roadmap. And what tradeoffs will that developer make regarding functionality, elegance and the release strategy. Best, Bill > > 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
