On Sun, Sep 28, 2008 at 4:48 AM, Linus Tolke <[EMAIL PROTECTED]> wrote:
> I have now made a plan i.e. set dates for the 0.28 release with the target > 11th of December. > > See the suggested release plan at > http://argouml.tigris.org/release_plan.html and give me comments. I've copied a summary of the release plan below so that everyone has the context for the discussion. My comments follow below. --------------------------------------- 2008-10-02 0.27.1 * New sequence diagrams? * New property panels? (Christian's GSoC work). * Improvements to diagrams? (Bogdan's GSoC work). * C# code generation (Thilina's GSoC work). * Improved Critics Subsystem (Marcos' GSoC work). * Move the User Manual out of the main project and into the argouml-documentation project. * Move java support to separate module. * The work above is completed and about to be merged so don't do simple code-improvements until the merging is done to avoid complicating the merge work. 2008-10-17 Tigris site upgrade planned 2008-11-01 0.27.2 * Any fix that you want to work with. * Simple code-improvements: Checkstyle and findbugs warnings fixed. Removing deprecated stuff. 2008-11-12 0.28.ALPHA_1 - Functional freeze. Bug fixes only 2008-11-18 0.28.ALPHA_2 2008-11-24 0.28.ALPHA_3 2008-11-29 0.28.BETA_1 - Regressions & showstoppers only 2008-12-11 0.28 stable release ------------------------------------------------------------- My comments : - Brian Hudson mentioned some things that he wanted to get integrated to support ArgoEclipse work. Were these rejected or did he not provide sufficient information for planning purposes? - A release that's less than a week away can't have question marks in the plan. Presumably the release planning has been going on with the contributors via private email rather than on the dev list, but at this point they areeither in or out. If they can't commit to getting stuff ready this week, they are out unless you want to allow a second set of integrations in 0.27.2. - The contributors need to understand that they are not only committing to getting the integration done this week, but having fully production ready code available for users in 4-6 weeks. Anyone who fails to meet this date is going to negatively impact the plans of their fellow students. - The beta test period is too short. Apparently I've got fundamentally different views on this, but I think we saw during the the 0.26 release that a) most users don't test the alpha releases and b) it takes them a while to get the beta releases installed and provide useful feedback. There also needs to be at least one beta update or release candidate. On the flip side, you probably don't need so many alpha releases right on top of each other. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
