yup.. .the vote will run until it stops ;-) I'll be around on the mailing list but not IRC.
Thanks for looking at it. Cheers, On 07/07/06, ant elder <[EMAIL PROTECTED]> wrote:
I think the 72 hours is a minimum not an exact amount of time, the vote can keep running until you've got the necessary number of binding +1s. Its also not great that a large part of this will be over a weekend so you may end up needing to wait a bit longer. I'm far from being a C++ expert so so far I'm struggling to get this running. I need to stop for now but I will be back on it over the weekend, it would be great if some of you C++ guys could be around on the mailing list and IRC to answer any questions about C++ setup I may have. Thanks, ...ant On 7/6/06, Pete Robbins <[EMAIL PROTECTED]> wrote: > > I have posted a candidate for the first C++ release here: > > http://people.apache.org/~robbinspg/RC1 > > The code is tagged in svn: > > http://svn.apache.org/repos/asf/incubator/tuscany/tags/cpp-0.1.incubating-M1/ > < > http://svn.apache.org/repos/asf/incubator/tuscany/tags/cpp-0.1.incubating-M1/%C2%A0 > > > > > Please vote to publish the Milestone 1 release distributions. Please > take some time to download the distributions, review them and test them > in your environment before voting. > > The vote is open for the next 72 hours, please vote by July 9th, > 23:00 BST. At least three +1 votes are required, and only the votes from > Tuscany committers are binding. If the majority of all votes is > positive, I will send a summary of that vote to the Incubator's general > list to formally request the Incubator PMC to approve the Tuscany C++ > Milestone 1 release. For your reference the Incubator release policy > guidelines are available at > http://incubator.apache.org/incubation/Incubation_Policy.html#Releases. > > > Release Summary > ============= > > Tuscany SCA C++ provides a runtime implementation for the Service > Component > Architecture 0.9 specification, written in C++ and will currently support > C++ > component implementation types. This is not yet a complete implementation > and > known restrictions are described below. > > Supported SCA Assembly Model features > * All features are supported unless listed under the known restrictions > below. See SCA Assembly Model specification. > > Supported language bindings > * Component implementations written in C++. See SCA Client and > Implementation Model specification. > * Component interfaces described by C++ classes. See SCA Client and > Implementation Model specification. > > Supported external service and entry point bindings > * The web service binding is supported. This implementation will support > web services which using document literal SOAP bindings conforming to > the > WS-I basic profile (rpc/encoded is not yet supported). > > Known restrictions > * Subsystem: wiring, entry points and external services are not > supported. > * Local service interfaces cannot use overloaded operations (the SCA > specification limits remote service interfaces to not using > overloaded operations). > * Each WSDL definition for a web service binding must be in a single > WSDL > document. > * No load time validation of the deployed SCA application (run time > validation only). > * No metadata API. > > A sample is included which demonstrates deploying an SCA module, component > wiring, locating and invoking C++ service from C++ component, invoking > from > a C++ client, and exposing a service as a web service using ws binding. > > > Cheers, > > -- > Pete > >
-- Pete
