I think the best we can do is make a mini-release and keep working on the "trunk". If some people have the old code in production, they would like to get the REST one asap, for many reasons, and they will have to migrate their code, so its better doing a mini-release than tell people (who not all are reading the mailing list everyday) to stay at X revision. My 2 cents.
G.- On Wed, Jul 16, 2008 at 2:59 PM, Cassie <[EMAIL PROTECTED]> wrote: > Now that we've decided on a path for the restful java code it's time to > figure out how we are going to deprecate the non-rest old code. (ie > GadgetDataServlet and friends). I know people are using the old code in > prod > so it needs to live somewhere and I'm not sure what the proper thing to do > in svn is. > > - do we branch in svn and put the old code on the branch? (i think the new > rest code should definitely be in "main") > - do we just tell people to stay at revision xxx if they want it? > - do we do a mini-release? > > It is probably something else I haven't thought of at all. And php guys - > you will probably have to do this too, so we should probably share the same > decision. > Thanks again for all feedback. > > - Cassie > > ps - just think, we almost have a clean social-api codebase! >
