You should be in good shape either way, actually. The same project structure will work with either SDK version, so you can retain the option to switch back and forth. The only "one-way" choice would be if you start using the new UiBinder, ClientBundle, and layout panel stuff. If you need to play it conservatively, you could hold off on those things, but you can at least start using the new in-browser development mode, which should make you even more productive as you push toward your own launch.
Big picture, though, we're eager to finalize 2.0, so I wouldn't expect too long an RC cycle this time. In other words, you should even be safe to start using 2.0-only features in the timeframe you're describing. On Nov 17, 2:23 pm, Yozons Support on Gmail <yoz...@gmail.com> wrote: > What's the ETA now for GWT 2.0 final? I am developing now under 1.7.1, but > won't expect to be in production for another 4 months or so. Would I be > better off getting a jump on 2.0 now or would I risk 2.0 not being ready for > production over the next several months? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=.
