adding some node.js specific extensions to the JavaScript compiler
might break the JavaScript support. I see no urgent need for node.js
Issues to be integrated, as long as we do not have a testsuite for
node.js. => postpone?
The most important Debian Package is probably the compiler, if there
is no specific need for erlang, we should just remove erlang from the
Debian Packaging definitions.
-roger
Quoting Niraj Tolia <nto...@maginatics.com>:
Hi Jake,
Is there any change of
https://issues.apache.org/jira/browse/THRIFT-1394 making it into this
release? I realize that it is only C++/Java but hopefully Diwaker or
others can contribute similar patches for the other languages.
Cheers,
Niraj
On Tue, Nov 8, 2011 at 6:05 PM, Jake Farrell <jfarr...@apache.org> wrote:
Roger
I have been trying to get ready for an rc over the past week and
there are a couple of tickets I was waiting on before proceeding.
I can create the 0.8.0-rc1 once we decide on the following
-Jake
Thrift-1330 & 1392: php namespaces (fix in progress)
Thrift-1421: debian package broken due to erlang (easy fix, remove
erlang until jsx is fixed)
Thrift-1401: delphi json (waiting on someone to +1)
Thrift-1267: node.js Exceptions (waiting on test cases)
Thrift-1277: node.js booleans as null (broke lint test)
On Nov 8, 2011, at 5:59 PM, Roger Meier wrote:
Yes
-roger
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
