I have now fixed the two dates problem. Sorry about that.
/Linus
2008/9/6 Bob Tarling <[EMAIL PROTECTED]>
> I notice there is a public google calendar embedded in our release
> timetable pages. For those using google calandar themselves it may be
> worth adding this to your own calendar displays (I did "add public
> calendar" and then searched for argouml).
>
> I notice though that there are two dates on that calendar for the next
> beta. Who owns the calendar to update it?
>
> How about using just this facility from now on rather than duplicate
> in html structure?
>
> Bob.
>
>
> 2008/9/4 Linus Tolke <[EMAIL PROTECTED]>:
> > The release plan is now updated to a more realistic one. This sets the
> date
> > for the 0.26 release to the 18th of September. I hope this is a good plan
> > now.
> >
> > /Linus
> >
> > 2008/9/4 Linus Tolke <[EMAIL PROTECTED]>
> >>
> >> OK. I will change the beta period plan to be longer and include several
> >> beta releases one week apart. This means that the second beta will be
> moved
> >> to Saturday then.
> >>
> >> I think I squeezed the beta period to this short when we tried to fit in
> >> the release before the start of the GSoC and since then I have just
> moved it
> >> along without making it longer.
> >>
> >> I though I had approved the message that Thomas wrote a few days ago. I
> >> must have forgotten about it in all the hurrying along. It is now
> approved.
> >> Alas it keeps the date from when Thomas created it. I will manually
> update
> >> to todays date to make it clearer when the announcement was made.
> >>
> >> /Linus
> >>
> >> 2008/9/4 Tom Morris <[EMAIL PROTECTED]>
> >>>
> >>> On Wed, Sep 3, 2008 at 4:47 PM, Linus Tolke <[EMAIL PROTECTED]> wrote:
> >>> > I would like the issue 5355 (the only P2 issue) to have a plan before
> >>> > we do
> >>> > the second beta so I will to tomorrow evening and not do the release
> >>> > today.
> >>>
> >>> Not all of my Eclipse workspaces for ArgoUML include the www tree, so
> >>> the only time I see that the schedule has been changed is when it's
> >>> announced on the list.
> >>>
> >>> I'm not sure when the current schedule was created, but it doesn't
> >>> seem reasonable to me to have a two month alpha period followed by ONE
> >>> WEEK beta period. For a beta test to be effective, the users have to
> >>> have time to get the announcement, schedule the testing in among their
> >>> regular work, then report the results back to us.
> >>>
> >>> Even if we were to convince ourselves that we'd get effective end user
> >>> testing (and reporting of those tests) in a week, surely you can't
> >>> start the clock until the release has actually been announced (which
> >>> it hasn't yet).
> >>>
> >>> Tom
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >>> For additional commands, e-mail: [EMAIL PROTECTED]
> >>>
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
