That reminds me,
I believe the banch is ready for release, if we accept that it will
have bugs and shortcommings and does not officially include the /java/
samples tree.
But there are 6 issues that need decisions.
Blockers:
SHINDIG-695(bug): I suspect this might not be a blocker, there is a
patch of sorts, but no grant of license so cant be used. Needs someone
more who knows the details of the Gadget Server well to downgrade or
close.
SHINDIG-561(feature socialAPI): The only comment on this gives the
impression this is about Gadgets, but I think Cassie was thinking
about the Social API. The RPC servlet is JSON specific in the Social
API, but if n XML servlet was written it would be possible to handle
XML-RPC request. In 0.8.1 the XML spec is still slightly in flux and
so IMHO this should postponed beyond the release.
SHINDIG-560: there are patches attached that need review and commit to
close this.
Critical:
SHINDIG-787(bug, IMHO this is a blocker): Requires that SHINDIG-764 is
reverted, Henning probably needs to read comments on both of these to
check that thinking is now clear. (re, the RESTAPI implements the wire
spec and not the Javascript API)
SHINDIG-689: (javascript), if this is still and issue, needs to be
applied, or closed.
SHINDIG-545:(php) probably can postpone
Ian
On 13 Jan 2009, at 14:20, Chris Chabot wrote:
Hi Lini,
We have a stable release branch of shindig available at
http://svn.apache.org/repos/asf/incubator/shindig/branches/1.0.x-incubating/which
is being made ready for release and won't see any of the larger
changes that are happening due to the 0.9 support development.
Hopefully we'll have a stable release ready 'any day now' (give or
take a
few weeks), after then it'll be a lot easier since you can just
follow the
stable releases which will happen a lot less frequently then svn
updates.
-- Chris
On Tue, Jan 13, 2009 at 10:26 AM, Lini H - Clarion, India <
[email protected]> wrote:
Hi,
I have a query regarding the shindig and the container deployment.
After I
deploy shinding in a site, how can I keep updating it with the new
updates
being added to shindig. Is there a permanent solution to this, or
will I
have to keep changing the shindig deployment as the new updates go
on to be
added?
Thanks & Regards,
Lini Haridas
Software Engineer
Clarion Technologies
SEI CMMI Level 3 Company
4th Floor, Great Eastern Plaza,
Airport Road,
Pune- 411 006,
Maharashtra, India.
www.clariontechnologies.co.in
Email: [email protected]
Mobile: +91 9823435917
