Hello all! 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. /Linus 2008/9/27 Linus Tolke <[EMAIL PROTECTED]> > Hello Tom! > > I am thinking quick as in "this year" which is very much like your three > months. The Release Plan page lists the GSoC things that I hope will be > integrated. > > What I have forgotten about that I would also like to see in the 0.28 is > the move of the java code generation and the new sequence diagrams. I think > they are both ready and waiting to be included. I will add them. > > I hope you agree. > > /Linus > > > > 2008/9/27 Tom Morris <[EMAIL PROTECTED]> > > So what is the timeframe and scope for 0.28? I heard several people >> say that they were interested in a "quick" release incorporating the >> 2008 GSoC projects, but I didn't see a decision one way or the other. >> >> Someone (Christian?) mentioned six months as a time for the quick >> release. That doesn't seem at all "quick" to me. I think the focus >> should be on projects that are really done and are ready to be >> integrated. If there's something that's 80% complete, that should >> wait until the next release. If the focus is kept purely on >> integrating existing working code, the release schedule should look >> more like three months than six months, in my opinion. >> >> Tom >> >> On Sat, Sep 27, 2008 at 4:09 PM, Linus Tolke <[EMAIL PROTECTED]> wrote: >> > Hello all! >> > >> > Here is the plan for the future releases and repository paths. This is >> so >> > that it is clear for everyone what the plan is. >> > >> > /trunk goes towards 0.27.1, 0.27.2, ... 0.28. When I will give you the >> green >> > light for committing things towards the next release. >> > >> > /releases/VERSION_0_26 is the stable release. >> > >> > If we decide to make a stable update release it will be called 0.26.1 >> and it >> > will be based on what is in /release/VERSION_0_26 and I will create a >> branch >> > from there for the release work. That update release will then be in >> > /release/VERSION_0_26_1. If you work on things that you want to put into >> > that release, create a branch from /releases/VERSION_0_26/<project> >> named >> > after your issue in /branches. The work can then easily be merged into >> the >> > release branch. >> > >> > /Linus >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >
