> It isn't easy to plan ahead if you have a fixed schedule for your project. > There's no point in developing against a release candidate for the next > version of GWT if you have to go live in May next year and you don't even > know if the next stable version is coming out in the first or second half of > the year.
This may be true for most organizations, but I don't think it applies to Google. As most of us know, Google's unstable beta releases are much higher quality then a lot of organizations' final releases that have been out there for several years. The real problem comes down to management accepting that argument. Regards, Arthur Kalmenson On Oct 8, 1:18 pm, "Ian Bambury" <[EMAIL PROTECTED]> wrote: > It isn't easy to plan ahead if you have a fixed schedule for your project. > There's no point in developing against a release candidate for the next > version of GWT if you have to go live in May next year and you don't even > know if the next stable version is coming out in the first or second half of > the year. > > Ian > > http://examples.roughian.com > > 2008/10/8 Ian Petersen [EMAIL PROTECTED] > > > > > I guess I was just taking issue with the claim that > > Google makes it impossible to plan ahead. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
