I have one fix to work on and a couple of others to commit.

Of the other issues the only one that concerns me at the moment is
http://argouml.tigris.org/issues/show_bug.cgi?id=4318

My concern is only based on the reporters comments that this prevents
him working with AndroMDA. I'm not AndroMDA savvy so I can't weigh
this up myself but I'd like to be sure that the AndroMDA community
give positive feedback to our next stable release. Is there any chance
of getting a fix for this before we go final?

I do think we need a longer period of verification before we go live
and also give beta testers more time to find high priority bugs. The
7th would be long enough I should think.

How shall we okay whether fixes can be applied in Linus absence?

I suggest we still post patches for peer review. P1/P2 issues should
be commited if any peer agrees.

Bob.


On 7/20/06, Linus Tolke <[EMAIL PROTECTED]> wrote:



Hello all!



Because of the fact that there are late fixes and late found problems in
0.22.beta2 I have introduced a 0.22.beta3 release. My plan for the upcoming
three weeks is now in an
"even-a-small-change-has-a-big-impact"-state. Like this:



Friday 21st – Tomorrow – 0.22.beta3 release.

Saturday through Tuesday – Linus is offline (vacation trip)

Monday 24th (will have to be moved to Wednesday) – 0.22 stable release

Thursday 27th through Monday 7th – Linus is offline (vacation trip)



This means that the slightest problem found in 0.22.beta3 moves the stable
release to after August 7th.



With the amount of problems that has appeared in 0.22.beta2 (already) and
the kinds of problems, it is perhaps better to plan the stable release for
after August the 7th and have a betas released on the 26th and on the 8th.



            /Linus



*******************************************************************

Linus Tolke
[EMAIL PROTECTED]    [EMAIL PROTECTED]
*******************************************************************



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to