Hi, IMNSHO I think that the best idea would be to host the new "gwt-rpc" project outside the project have a completely separate moniker - something that offers easy iconography (Mmmm ... TigerRPC?). Once it is stabilised and offers a credible alternative to current gwt-rpc, at that point I think it would be good to start documenting it as the spiritual successor of gwt-rpc.
The advantage of this approach is that you get to iterate much faster with a lot less overhead. You also potentially get developers involved that have the time/interest to work on that specific project. -- Cheers, Peter Donald -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc5G0KHqZpY_tTKxojP36gwyQDHh1XVPY%2BsH4Wk59ntkew%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
