Pete,
Sorry that I missed this the first time around. I think keeping
them separate is best, either in separate zip files or in separate
directories within a single installation. Separate zip files seems
slightly more work as it increases the installation testing needed
to ensure that both the
In the Tuscany C++ source tree we have a subproject for SDO and one for SCA
(which prereqs the SDO build). For a binary release should we combine the
build output into a single zip ro have a separate SDO zip?
If we do combine them we have a further option of the unzipped layout having
a separate
OK... as I need to start on this several days ago I'm going to produce
seeparate zips for SDO and SCA.
On 08/06/06, Pete Robbins [EMAIL PROTECTED] wrote:
In the Tuscany C++ source tree we have a subproject for SDO and one for
SCA (which prereqs the SDO build). For a binary release should we
, but
jun16 is not going to be possible - we will have to think of a simpler
sample
haleh let's focus on having a good content and quality first. This is the
first time we have a C++ release. First impression is important
robbinspg I put a draft things-to-do wiki page up with what I would
consider
As we work towards a binary C++ release we need to elect a release manager.
I'm happy to volunteer for this.
--
Pete
+1 for Pete as RM for this C++ release
...ant
On 6/7/06, Pete Robbins [EMAIL PROTECTED] wrote:
As we work towards a binary C++ release we need to elect a release
manager.
I'm happy to volunteer for this.
--
Pete
Pete Robbins wrote:
As we work towards a binary C++ release we need to elect a release
manager.
I'm happy to volunteer for this.
+1 from me.
--
Jean-Sebastien
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
+1 from me as well.
Simon
Daniel Kulp wrote:
I'll +1 for Pete. It's always good to see a volunteer. :-)
Dan
On Wednesday June 07 2006 4:28 am, Pete Robbins wrote:
As we work towards a binary C++ release we need to elect a release manager.
I'm happy to volunteer
A reminder:
We will have an IRC chat on Tuesday 6th June 17:00 BST (18:00 GMT) 12:00
(Eastern) 09:00 (Pacific) to finalize content and schedule to achieve this.
Any input from Java Tuscans on their recent release experience would be
welcome.
The chat takes place on the freenode IRC network,
+1 from me too, but aplogies, I can't make the IRC chat.
On 5/25/06, Pete Robbins [EMAIL PROTECTED] wrote:
As mentioned previously we would be a like to have a binary release of the
C++ code by ApacheCon Europe.
I'd like to propose an IRC chat on Tuesday 6th June 17:00 BST (18:00 GMT)
12:00
+1 for the release, but i can't make an IRC chat on Tuesday sorry.
...ant
On 5/25/06, Pete Robbins [EMAIL PROTECTED] wrote:
As mentioned previously we would be a like to have a binary release of the
C++ code by ApacheCon Europe.
I'd like to propose an IRC chat on Tuesday 6th June 17:00 BST
Pete
+1 for release and IRC chat
On 5/25/06, Pete Robbins [EMAIL PROTECTED] wrote:
As mentioned previously we would be a like to have a binary release of the
C++ code by ApacheCon Europe.
I'd like to propose an IRC chat on Tuesday 6th June 17:00 BST (18:00 GMT)
12:00 (Eastern) 09:00
Pete,
another +1 for the release and IRC chat
+1 from me too.
As well as the list of tasks that's on the Wiki, it would be good to discuss
a list of functionality that will be in the release - I seem to remember
seeing a list somewhere - does anyone know where or was it just my
overactive imagination?
Cheers
Andrew
As mentioned previously we would be a like to have a binary release of the
C++ code by ApacheCon Europe.
I'd like to propose an IRC chat on Tuesday 6th June 17:00 BST (18:00 GMT)
12:00 (Eastern) 09:00 (Pacific) to finalize content and schedule to achieve
this.
As a starting point, and for
+1.
From the SDO C++ point of view, the interop that could be done by then would
be at the serialized level - I.E being able to load/save the same XML in
both systems.
In terms of Axis2C support, I am looking into providing a utility to write
AXIOM from SDOs and SDO types. Ideally I would do
+1
Following on from Ed's point. I'm working my way through doing some simple
read/write interop test for PHP/C++/Java XML at the moment initially based
on the company data example. However to make this a useful test it would
seem sensible to make a schema that contains all of the simple and
A separate thread to discuss SCA/SDO interop testing sounds like a good
idea.
I'd like to focus here on what we need to complete to have a viable binary
release: code(functional content), documentation, testing, samples... etc.
and then come up with a timetable/ordering of the tasks.
Cheers,
--
18 matches
Mail list logo
