Sebastien, good to have you on board!

Please feel free to update the doc if you see anything that needs doing. I
hope to have an RC3 available today which has (hopefully) better doc and
also samples added in to the SDO distribution. I think the only thing
missing is the doc on running the SDO samples.

Go ahead and set the svn-ignore properties too if you like. We should have
done this before now!

Cheers,


On 17/07/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:

Hi,

I would like to start contributing to the Tuscany C++ implementation. I
know that you're all in the middle of freezing the C++ M1 release, are
there any areas in particular where I can help? It's probably not the
right time to introduce any breaking code changes :) but maybe I can
help with testing or any minor documentation fixes?

So far I've tested the M1 RC2 SCA source distributions and also rebuilt
the runtime and samples from the SVN head on Linux Redhat EL4. I
followed the steps in build.txt and GettingStarted and found them pretty
straightforward.

The source distributions look good to me. I was able to run the SCA
Calculator sample without any problem. I only ran into a few minor
things that do not actually impact the release.
- The build.txt under tuscany/cpp/ talks about libxml2 2.6.19 but Axis2
0.92 requires 2.6.20. The GettingStarted doc that ships with the release
is correct and says 2.6.20, so people who download the release will be OK.
- It would be nice to set the svn:ignore properties to allow SVN to
ignore all the files generated by the build, and not running the risk of
people checking these files in by mistake.

I can take care of these two changes if you want, but let me know what
you prefer... I really don't want to disrupt your release freeze process
and introduce changes while you're releasing and tagging... Thanks.

--
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




--
Pete

Reply via email to