-----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-----
