+1 for Pete as RM from me as well. ...ant
On 1/26/07, Andrew Borley <[EMAIL PROTECTED]> wrote:
On 1/26/07, Pete Robbins <[EMAIL PROTECTED]> wrote: > On 26/01/07, Pete Robbins <[EMAIL PROTECTED]> wrote: > > > > > > > > On 26/01/07, Andrew Borley <[EMAIL PROTECTED]> wrote: > > > > > > On 1/20/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > > > [snip] > > > > Pete Robbins wrote: > > > > > On 19/01/07, Andrew Borley <[EMAIL PROTECTED]> wrote: > > > > >> > > > > >> Hi all, > > > > >> > > > > >> Since the Tuscany C++ M2 release, there's been quite a bit of extra > > > > > > > >> functionality added to the codebase, so perhaps we should start > > > > >> thinking about an M3 release? > > > > >> > > > > >> Things added: > > > > >> - REST service & reference binding > > > > >> - Support for multi-threaded environments > > > > >> - Support for Apache HTTPD (both for REST and Axis2 ws service > > > bindings) > > > > >> - Removal of componentType side-file requirement for Python > > > components > > > > >> - SDO support in Python components > > > > >> - Named-argument support for REST references, Python and C++ > > > components > > > > >> - Samples that show use of above functionality > > > > >> - 'Real-world' samples showing calls to externally available > > > services > > > > >> - Mac OSX port (not sure if this is complete?) > > > > > > > > > > > > > > > Not complete. SDO is fine but I need to do some more work on SCA. > > > I've > > > > > been > > > > > having trouble getting Ruby to load our extension. Also, Axis2C does > > > not > > > > > support MacOS so I need to partition the build to only include > > > non-Axis > > > > > samples. > > > > > > > > > > > > > The spec collaboration has agreed to remove the requirement that an > > > SCA > > > > runtime MUST provide support for the Web Service binding (see > > > > https://issues.apache.org/jira/browse/TUSCANY-984). So we can > > > completely > > > > omit the WS binding extension and the WS binding based samples on > > > MacOS > > > > for now. > > > > > > > > > When we get this working the source release will be the same as > > > Linux. > > > > > Should we deliver a MacOS binary? > > > > > > > > > > > > > +1. If it's not too much work (I assume the binary distribution will > > > be > > > > very similar to the Linux one) that will be great! > > > > > > > > -- > > > > Jean-Sebastien > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > We've had no volunteers for the release manager job - I'm happy to do > > > it again if people want me to! I haven't access to a Mac OSX box, so > > > someone else will have to build/test a binary distro if we're doing > > > one. > > > > > > Cheers > > > Andy > > > > > > I'll volunteer for RM as you did it last time... if you like? Either way > > I'm happy to build/test on Mac OS X. > > > > > > Forgot to say I'm away with no access from 3rd - 11th Feb so depending on > when we want to start building/publishing release candidates that may be a > problem. > +1 for Pete as RM! If we can get an RC1 sorted out before you're away then we can spend that week testing, fixing, improving documentation, etc. If RC1 is deemed good (it could happen!), then I'm sure we can wait a few extra days before proposing it to the incubator board. Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
