The thread on sequence diagrams introduced the topic of planning for the release of 0.26. I think this is important enough to deserve a discussion of its own.
Our last public release, 0.24, was 15 Feb 2007 after a 1 week beta period. Our last developer release was 0.25.2 in Apr 2007 (not counting the May 2007 release of 0.25.3 which we withdrew). Given the holidays, an appropriate period of beta testing, and whatever cleanup work needs to be done, we'd probably be looking at mid-February to get what we have out the door. Adding more work will obviously extend the schedule. >From a global perspective, general releases much more than a year apart are undesirable unless there's strong motivation for it, in my opinion. Also, we should plan on being included in the Google Summer of Code again and thus plan to have the source pool (or a branch of it) ready for students at the beginning of the summer. GSoC will also have an impact on the manpower we have available since the application review period is a labor intensive one. If we're changing licenses, I believe we should do it before the release. I don't know if we allow a non-contributor to successfully filibuster the decision to death or if Linus is still planning to drive this to a decision. If we change, that work needs to be factored into the release plan. It's probably just running a script over the sources and updating checkstyle, but all the little things add up. What are our goals/themes for 0.26? (Yes, it's late to be discussing this) - Profiles - the core is already integrated, but there are probably loose ends to clean up. Also not clear how much testing its gotten. - Sequence Diagram reimplementation? - sounds like we've got at least a couple of votes for this - Multi-file support? - I did the basics to support the profile work and it probably wouldn't be a lot of work to enable it for general use, but I'm loathe to contribute any significant new functionality until the license issue is resolved - Scalability? - currently sucks for very large projects. Not clear how much work it would be to improve. Could be one or two critical bugs or a more general malaise. - Dependency cycles? - not a user visible item, but it slows our refactoring and improving the code base, as well as our ability to work well in the Eclipse environment - Quality? - We've closed 67 unique, previously reported issues (126 total including duplicates and bugs that we introduced post-0.24) and we have 421 defects open (2 P1, 4 P2, 364 P3, 51 P4 & P5. We could make a push to close a bunch of bugs (or triage them all better and close some number of high impact ones). - Timeliness/Schedule - Any desired goals here? - ???? - insert your theme here. Suggestions? What are people's thoughts? When should we target the release? What should it include? Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
