Thanks to Jeremy to clearly state the objective and explain the strategy.
+1 from me.
Raymond
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Wednesday, October 11, 2006 4:49 PM
Subject: Stabilizing M2 for release
We have had quite
At 00:49 12/10/2006, Jeremy Boynes wrote:
I am not sure on whether javascript, jsonrpc, ruby or spring fall in
this category or the next - opinions?
Spring is stable enough IMO. I have some changes planned, but
probably not in time for M2 and the existing code works ok (and is
mostly
Generally favorable. Essentially +1 if it were a vote. I have one concern is on
the sca deliverables. We need to drive to a conclusion soon to figure out the
exact artifacts a user will download and what each will contain. Not directly,
related to the branching, but you did touched on it.
+1
I'll wait for 2 JIRAS to get in and I'll work with a commiter to get DAS
branch created.
- Luciano Resende
On 10/12/06, Rick [EMAIL PROTECTED] wrote:
Generally favorable. Essentially +1 if it were a vote. I have one concern
is on
the sca deliverables. We need to drive to a conclusion
Hi Jeremy, thanks for that explanation... was really useful.
I think Javascript and maybe even Ruby should be in.
Javascript has been up and working for long now. I found it to be a good
demonstration of a container extension and that is how I ended up doing Ruby
quickly (by my standards :)).
We have had quite a few suggestions over the last couple of days for
new functionality for the trunk some of which would result in changes
to the APIs. We have also had the completion of one of the major
pieces of code (async over axis webservices) that was still
outstanding although there
On Oct 11, 2006, at 4:49 PM, Jeremy Boynes wrote:
We have had quite a few suggestions over the last couple of days
for new functionality for the trunk some of which would result in
changes to the APIs. We have also had the completion of one of the
major pieces of code (async over axis
