Unfortunately, I found a pretty big bug. When we cut over to the new interface model, the rave-shindig classes began using the username as the opensocial id (similar to igoogle,etc) rather than the arbitrary database entity id. Unfortunately, when I made those changes, I didn't update the security token classes in rave portal. This means that any code in shindig that checks the security token id against the passed in userid will fail. This primarily affects appdata; which, IMO is a pretty big deal..
Apologies, but when you consider this with Ate's potential bug, I am not sure we should ship the release... >-----Original Message----- >From: Ate Douma [mailto:[email protected]] >Sent: Friday, June 29, 2012 7:43 PM >To: [email protected] >Subject: [DISCUSS] Apache Rave 0.13 Release Candidate > >Discussion thread for vote on 0.13 release candidate. > >For more information on the release process, checkout - >http://www.apache.org/dev/release.html > >Some of the things to check before voting are: >- can you run the demo binaries >- can you build the contents of source-release.zip and svn tag >- do all of the staged jars/zips contain the required LICENSE and NOTICE files >- are all of the staged artifacts signed and the signature verifiable >- is the signing key in the project's KEYS file and on a public server
