The 1.0 release (which supports 0.8.1) isn't really a development target anymore, I'd only accept patches for that for the most critical issues. We don't really want social sites to be stuck on 0.8 when 0.9 has already been out for a while, otherwise gadget devs could never start using 0.9 features. (do note: the 1.1 release will be compatible with OpenSocial 0.7, 0.8 and 0.9, backward compatibility is a hard requirement for us).
The current focus is on getting a 1.1 release done (with OpenSocial 0.9 support) and any new changes (like reverse proxy support) will be applied to that instead. On Tue, Jul 14, 2009 at 12:18 PM, Loic Dachary <l...@dachary.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > > I've seen that shindig-1.1 is on the way. In the past few weeks I've > worked to get shindig-1.0 working ( for a multiplayer poker > application ) and we submitted a few patches ( reverse proxy, cookie > handling, proxy error handing, all in JIRA ) against the shindig-1.0 > release. How will these be handled ? When 1.1 is out, will I need to > port them to the trunk in order for them to be taken into > consideration ? Or will it be enough to let them as they are and wait > for a commiter to find time to review / apply them ? > > Thanks in advance > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkpcW4wACgkQ8dLMyEl6F213/QCffBYQDUN31L2swSJ6rhcpUKcM > 9cIAoJu8RuvYBem2HWvZaD25WECeINjP > =cILa > -----END PGP SIGNATURE----- > >
