Tag Date On the release notes, I've proposed a tag date of Sunday, 4 March 2007, if that works for everyone.
Issues / Roadmap Traditionally, we have included new features in milestones so long as changes were backwardly compatible with the immediately previous GA API. We were just careful to keep each new GA milestone compatible with the last GA, but we never make any guarantees beyond that, meaning that 1.2.4 might not be binary compatible with 1.2.9 in some respects. Or, rather than tinker much with 2.0.x, we could just push anything that smells like a new feature into 2.1.x, minimize cross-commits, and get on with the 2.1.x release series. For the 2.0.x series, one exception to the "new features" policy might be items that are already part of the latest WebWork (e.g. WW-1678 "Cooke Interceptor"), and other items that speak to compatibility with Struts 1 ((WW-1350 "Autofocus"). I'm not sure about WW-1704 (ParameterFilterInterceptor). Unless this is part of WW2, it seems like something that we could push into S2.1.x. I silently moved 14 issues from 2.0.x to 2.0.7 (WW-1624, WW-1560, WW-1600, WW-1654, WW-1672, SS-1619, WW-1719, WW-1717, WW-1350, WW-1622, WW-1625, WW-1643, WW-1533), set them all to "minor" priority, and removed the 2.0.x meta-version. If we do not resolve these issues in 2.0.7, I'm thinking that we can push them to 2.0.8, 2.1.0, or the 2.x Future meta-version. Core Plugins This is more of a 2.1.x status item, but looking forward, do we want to bundle so many plugins with the core, or do we want to try and cut some of these loose somehow? Of course, there is also something to be said for "letting sleeping dogs lie". Commit Logs - Nice Work. Looking over the commit logs, we're doing a good job in referencing each commit with a JIRA ticket and summarizing the substance of a commit. Keep in mind that the logs are available through the release notes that JIRA generates, and they are available to posterity through the SVN web interface. Don't be shy about including details or summarizing any development discussions that lead up to the commit. Back in the day, Craig was known to post 500 word commit logs, and skip the dev list post altogether :) Also note that when resolving or closing cross-posted issues, we can select multiple versions (2.1.0, 2.0.7). Try not to select a "meta version" like "2.1.x" or "Future" when resolving or closing issues. (So anything logged against 2.1.x right now, if resolved or closed, should be a fix for 2.1.0 (even if "not a problem"). Likewise the "raised against" value should be a concrete release. If unsure, use the earliest in the series. Snippets rock! Now that we have a working macro (thanks Don!), the snippet approach to single-sourcing the documentation also seems to be working well. We need a few more glue pages like the "Creating Interceptor" page, but it looks to me like the current approach is creating a very helpful set of online docs that we can actually keep up to date! The beauty of snippets is that they encourage us to create better JavaDocs, and "top-shelf" JavaDocs have always been a Struts hallmark. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
