Colleagues, What should we aim for with Velocity 1.6?
I feel that we've cleaned up most urgent bugs and pressing issues with the 1.5 release. Given the sporadic nature of our development efforts, timelines are a little risky. Still, I was thinking it'd be nice to do a release of 1.6 this fall. JIRA lists 38 issues with a 1.6 target. There's a few bugs and a lot of incremental feature suggestions, few with actual code. Many of these enhancement requests will likely get bumped back unless someone champions them. https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=12310104&fixfor=12310290 What issues do our committer and developer community care about? I think we should have modest goals. Myself, I mostly want to see the macro issues addressed. I'd also like to clean up the project, split out Texen and Anakia (per Henning's suggestions on maintaining compatibility). I've written up a few notes at http://wiki.apache.org/velocity/RoadMap If one of the committers (Henning?) becomes fired up, we could start a 2.0 branch, though I confess that personally I'm more interested in incremental development. WILL -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
