Hi Dan, Chris,
I just had chat with Chris. I'll go with snapshooting certain revision and hopefully merge release branch later on, which should be OpenSocial v0.8 compliant. Thank you for your replies! 2008/6/5 Chris Chabot <[EMAIL PROTECTED]>: > We did have the goal to try to get a release process going once we hit 0.8 > compliance.. so that's the closest to a branching moment we currently have > planned. > > > On Jun 5, 2008, at 10:10 AM, Dan Peterson wrote: > >> I'm not aware of any plans to branch, but I think it is reasonably common >> to snapshot against a given change and iterate from there for your >> particular instance -- and merge against trunk later (to incorporate >> updates). >> >> -Dan >> >> >> >> >> ----- Original Message ----- >> From: Eiji Kitamura <[EMAIL PROTECTED]> >> To: [email protected] <[email protected]> >> Sent: Thu Jun 05 00:53:03 2008 >> Subject: Branching shindig repository >> >> Hi, >> >> >> Quick question. Is there any plan on branching shindig as compliant >> version for OpenSocial v0.7? >> php version and java version separately, maybe. >> >> I heard shindig is already v0.7 compliant (at least php version), but >> it's difficult to chase every changes made daily. We want to >> concentrate on fixed code (except for bug fixes) to deploy on our >> service . >> >> Is there any plan on branching? > >
