MacOS X build, was: Transcript of IRC chat on C++ M2 release
Andrew Borley wrote: Hi Oisin, On 10/4/06, Oisin Hurley <[EMAIL PROTECTED]> wrote: Hi guys, Sorry I couldn't make the IRC - had to run off to a night class. > 18:36:06what about MacOSX? there was a patch for that, > but I don't > know what the status is > 18:36:17I also don't have access to any mac machines > 18:36:19I'll do Mac OSX > 18:36:32so long as someone buys me a new PowerBook > 18:36:47for MacOSX the first question is: is Axis2C > shipping bins > on MacOSX? I can get a MacOSX build done for 0.94, but as you can see at [0], the priority on the patch is low. Looking at the current set of Jirae that are going in there it seems they have more pressing concerns. This brings up a question from me wot is ignorant of Apache devoirs in term of infrastructure support. Since I'm mostly doing Eclipse work, I'm used to having heaps of donated build machines that will do nightlys etc. I guess that this is not the case at Apache and that binary builds are done by project committers - or the most excellent release person :) Yep, that's right. I assume at the moment that there is no-one working on Mac OSX in Axis2C - I'm sure they would be very happy to have Mac OSX coverage if someone can provide the build & testing work. I will update the Axis patch to work with the current pre-0.94 base and see will they take it (it's not a new feature imho). That would be good - we decided near the end of the IRC chat to have a dependency on Axis2C 0.93 as we weren't sure exactly when 0.94 would be out and we'd like our first RC by the end of this week. Saying that, Sebastien put in a tiny code change which made Tuscany work with the latest Axis2C trunk, so the 0.94 release will hopefully work with Tuscany M2. If they don't, would it be a horrible gaffe to post an 'independent' set of binaries and headers as a supplemental download on the Tuscany site? I hope asking that question wasn't of itself a horrible gaffe :) I have no idea - I'm not sure if the Tuscany site is the best place to host an Axis2C MacOSX binary, but we could certainly point to one on another (perhaps independent?) site. Another option is to point to/provide the patches to enable OSXers to build Axis2C and then Tuscany. +1, if there's no better option then I think we should at least provide the patches and instructions to build Tuscany and its dependencies on MacOSX from source. Many people in open source communities now use MacOSX and without a MacOSX build they won't be able to work with Tuscany C++ at all. With all the effort that Oisin already put into it, I think it makes sense to at least publish these instructions and make clear that people can download our source distro and follow these instructions to build on MacOS X. 18:36:50:) do we want RC1 on OSX? Could anyone volunteer? > 18:37:12Good point - I doubt it > 18:37:22let's get RC1 out and see if the resulting src > release > can be built on Mac > 18:37:36we should ask oisin what he wants to do, since he > contributed that patch and tested it Consider me volunteered for build and test - I would consider that there is more important work to be done for RC1, so I'm not going to be insistent on it's inclusion. Cheers Oisin, that's great - I guess we won't have the time to get it into RC1, but we may be able to sort it out for a later RC. Great Oisin, thanks! As I said above I think it's really important to have a MacOS X build for all the MacOS X open source developers out there. Thanks! Andy -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Transcript of IRC chat on C++ M2 release
Quick clarification Andy - will you be shifting axis version before Milestone? Or saving it for after? It depends when 0.94 comes out I guess - if it's soon then shifting is probably a good idea (especially with some of the fixes that are planned for 0.94), but I don't think we should delay M2 specifically for 0.94. Does that sound OK? Sounds fair enough to me, thanks! cheers --oh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Transcript of IRC chat on C++ M2 release
On 10/4/06, Oisin Hurley <[EMAIL PROTECTED]> wrote: Quick clarification Andy - will you be shifting axis version before Milestone? Or saving it for after? It depends when 0.94 comes out I guess - if it's soon then shifting is probably a good idea (especially with some of the fixes that are planned for 0.94), but I don't think we should delay M2 specifically for 0.94. Does that sound OK? Cheers Andy
Re: Transcript of IRC chat on C++ M2 release
That would be good - we decided near the end of the IRC chat to have a dependency on Axis2C 0.93 as we weren't sure exactly when 0.94 would be out and we'd like our first RC by the end of this week. Saying that, Sebastien put in a tiny code change which made Tuscany work with the latest Axis2C trunk, so the 0.94 release will hopefully work with Tuscany M2. Ok, well I notice their code freeze was lifted there today, so I'll go see what I have to do to get a build together on 0.94. The 0.93 build did have some unit test failures on MacOS, it will be interesting to see if any of the current spate of updates has fixed these. I have no idea - I'm not sure if the Tuscany site is the best place to host an Axis2C MacOSX binary, but we could certainly point to one on another (perhaps independent?) site. Another option is to point to/provide the patches to enable OSXers to build Axis2C and then Tuscany. If I get a build and test clean, I will do some volunteering to do the builds and tests for the Axis2C guys in the interim so maybe they will host the bin build. Cheers Oisin, that's great - I guess we won't have the time to get it into RC1, but we may be able to sort it out for a later RC. Quick clarification Andy - will you be shifting axis version before Milestone? Or saving it for after? cheers --oh - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [C++] M2 Release
Following the IRC chat last night, I've put up the items we decided on and who volunteered for them at http://wiki.apache.org/ws/Tuscany/TuscanyCpp/Tasks. I have also raised & assigned Jiras - see the list that have been assigned to Fix-for Cpp-M2. Cheers! Andy On 10/2/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: Pete Robbins wrote: > I think we should find a time tomorrow. I'm fairly flexible. 6pm BST (5pm > GMT, 10am Pacific) may fit best. > > On 02/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: >> >> Hi Pete, >> >> Thanks for the licence text stuff. Yep, an IRC chat & tracking items >> via Jiras would be cool. When would be a good time for a chat? For me, >> tomorrow 4 til 5pm BST or Wednesday 5 til 6pm are both free. Good for >> anyone else? >> >> Cheers >> Andy >> >> >> On 10/2/06, Pete Robbins <[EMAIL PROTECTED]> wrote: >> > Andy, >> > >> > I'll do the change to the new licence text (hopefully tomorrow). >> > Should we have an IRC chat to prioritise outstanding items and >> Jiras? Is >> is >> > good to raise Jiras for all the work items such as doc etc so we can >> track >> > what get checked in from now up to the release. If we are trying to >> close >> > down for a release we should only be checking in for items that we >> need >> for >> > the release. >> > >> > Cheers, >> > >> > >> > On 02/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: >> > > >> > > Hi All, >> > > >> > > I think it would be good if we could get our first release candidate >> > > cut by or during ApacheCon (which is next week!) - do people think >> > > that is possible? >> > > >> > > With this in mind I propose we concentrate on the higher priority >> > > stuff, which to my mind is documentation, samples, build >> requirements >> > > (licencing, build files, etc), the PHP extension and the support >> for a >> > > particular spec level. >> > > >> > > Do people agree with this? Is there some particular >> functionality/bug >> > > fix that should go in? >> > > >> > > Cheers >> > > >> > > Andy >> > > >> > > >> - >> > > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > > For additional commands, e-mail: [EMAIL PROTECTED] >> > > >> > > >> > >> > >> > -- >> > Pete >> > >> > >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > 10am PDT works for me. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Transcript of IRC chat on C++ M2 release
Hi Oisin, On 10/4/06, Oisin Hurley <[EMAIL PROTECTED]> wrote: Hi guys, Sorry I couldn't make the IRC - had to run off to a night class. > 18:36:06what about MacOSX? there was a patch for that, > but I don't > know what the status is > 18:36:17I also don't have access to any mac machines > 18:36:19I'll do Mac OSX > 18:36:32so long as someone buys me a new PowerBook > 18:36:47for MacOSX the first question is: is Axis2C > shipping bins > on MacOSX? I can get a MacOSX build done for 0.94, but as you can see at [0], the priority on the patch is low. Looking at the current set of Jirae that are going in there it seems they have more pressing concerns. This brings up a question from me wot is ignorant of Apache devoirs in term of infrastructure support. Since I'm mostly doing Eclipse work, I'm used to having heaps of donated build machines that will do nightlys etc. I guess that this is not the case at Apache and that binary builds are done by project committers - or the most excellent release person :) Yep, that's right. I assume at the moment that there is no-one working on Mac OSX in Axis2C - I'm sure they would be very happy to have Mac OSX coverage if someone can provide the build & testing work. I will update the Axis patch to work with the current pre-0.94 base and see will they take it (it's not a new feature imho). That would be good - we decided near the end of the IRC chat to have a dependency on Axis2C 0.93 as we weren't sure exactly when 0.94 would be out and we'd like our first RC by the end of this week. Saying that, Sebastien put in a tiny code change which made Tuscany work with the latest Axis2C trunk, so the 0.94 release will hopefully work with Tuscany M2. If they don't, would it be a horrible gaffe to post an 'independent' set of binaries and headers as a supplemental download on the Tuscany site? I hope asking that question wasn't of itself a horrible gaffe :) I have no idea - I'm not sure if the Tuscany site is the best place to host an Axis2C MacOSX binary, but we could certainly point to one on another (perhaps independent?) site. Another option is to point to/provide the patches to enable OSXers to build Axis2C and then Tuscany. 18:36:50:) do we want RC1 on OSX? Could anyone volunteer? > 18:37:12Good point - I doubt it > 18:37:22let's get RC1 out and see if the resulting src > release > can be built on Mac > 18:37:36we should ask oisin what he wants to do, since he > contributed that patch and tested it Consider me volunteered for build and test - I would consider that there is more important work to be done for RC1, so I'm not going to be insistent on it's inclusion. Cheers Oisin, that's great - I guess we won't have the time to get it into RC1, but we may be able to sort it out for a later RC. Thanks! Andy
Re: Transcript of IRC chat on C++ M2 release
Hi guys, Sorry I couldn't make the IRC - had to run off to a night class. 18:36:06what about MacOSX? there was a patch for that, but I don't know what the status is 18:36:17I also don't have access to any mac machines 18:36:19I'll do Mac OSX 18:36:32so long as someone buys me a new PowerBook 18:36:47for MacOSX the first question is: is Axis2C shipping bins on MacOSX? I can get a MacOSX build done for 0.94, but as you can see at [0], the priority on the patch is low. Looking at the current set of Jirae that are going in there it seems they have more pressing concerns. This brings up a question from me wot is ignorant of Apache devoirs in term of infrastructure support. Since I'm mostly doing Eclipse work, I'm used to having heaps of donated build machines that will do nightlys etc. I guess that this is not the case at Apache and that binary builds are done by project committers - or the most excellent release person :) I will update the Axis patch to work with the current pre-0.94 base and see will they take it (it's not a new feature imho). If they don't, would it be a horrible gaffe to post an 'independent' set of binaries and headers as a supplemental download on the Tuscany site? I hope asking that question wasn't of itself a horrible gaffe :) 18:36:50:) do we want RC1 on OSX? Could anyone volunteer? 18:37:12Good point - I doubt it 18:37:22let's get RC1 out and see if the resulting src release can be built on Mac 18:37:36we should ask oisin what he wants to do, since he contributed that patch and tested it Consider me volunteered for build and test - I would consider that there is more important work to be done for RC1, so I'm not going to be insistent on it's inclusion. cheers --oh [0] https://issues.apache.org/jira/browse/AXIS2C-287 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Transcript of IRC chat on C++ M2 release
Hi all, We just had a good IRC chat about the forthcoming Tuscany C++ M2 release. Main things decided: - We will try to get Release Candidate 1 out by end of this week/early next - Items in RC1 have been decided & volunteered for, the list will be available at http://wiki.apache.org/ws/Tuscany/TuscanyCpp/Tasks (when I've done it) Transcript below. Cheers! Andy 18:00:29tick tock ... it's 18:00 BST 18:00:35Hi all - my clock says it's 18:00 - good to go? 18:00:43Pete beat me to it 18:01:02I live slightly further east than you ;-) 18:01:03hey 18:01:27Are you going to run this Andy? 18:01:41Yep, I'm happy to run this 18:01:49OK, so we've put a list of items up on the wiki 18:02:03http://wiki.apache.org/ws/Tuscany/TuscanyCpp/Tasks 18:02:34and there's a lot there, I expect quite a few things won't make it if we want to get a first RC out by the end of this week 18:02:57So, the first question is - is an RC by the end of the week a good idea? 18:03:15Any items that really should go in & will take more than a week? 18:03:47The first RC does not have to be perfect and I'd like to see us have the infrastructure to make the release in place 18:04:14so we know we can turn the handle and create a RC 18:04:16yes, I guess the first RC is there to allow us to polish the build infra 18:04:22Yep sounds good - do you think the infrastructure can be updated by the end of the week? 18:04:46that means getting the licence stuff correct and a working build and package on linux and windows 18:05:05yes I think it's doable 18:05:08Yep - doesn't look too bad 18:05:37-->|slaws ([EMAIL PROTECTED]/ibm/x-4d3c867d81249199) has joined #tuscany 18:05:52what do we need to do to the Linux build? is it good as of today? 18:05:56so I'm currently updating the licence info so mark that one down to me 18:06:30The linux build is ok but we need to make sure that make dist works 18:06:40I think te linux build is mostly good - not sure what the script that packages bin and src distros is good 18:06:59and that the resulting distro contains all the right stuff to enable ./configure, make in the samples 18:07:13That took some work for M1 18:07:20ah ok, I can help test the linux build if it helps 18:07:45great - thanks 18:08:19Should we go through the list to decide if items should be in or out? 18:08:24Windows is built via a bat which basically runs the vc6 compile followed by copying/zipping 18:08:54are we building with vc6, 7 or 8 for this release? 18:09:04ok. How up-to-date are the vc7 files? 18:09:11sorry vc6 18:09:33I think we still have an issue with vc8 18:09:46I vote we stay with vc6 for this releas 18:09:58I know vc7 is good, but I don't have a vc6 system 18:10:17VC6 projects don't work at all at the moment but are easily fixable 18:10:21which version of vc7? 18:10:28Pete - could you do vc6 things for the release? 18:10:35it;s the generating of the batch makefiles which makes vc6 attractive 18:10:36I think mine is vc7.1 18:10:39-->|jmarino ([EMAIL PROTECTED]) has joined #tuscany 18:10:45Pete - agreed 18:10:54I suggest we stick to one, and maybe even take out the other versions, it's a little confusing to have multiple versions of the project files, some up to date, some outdated 18:10:56it's nice to have a command line build 18:10:59if pete can generate the make can we use them? 18:11:19Yep, vc6 make worked with vc7 last time 18:11:27-->|gwinn ([EMAIL PROTECTED]) has joined #tuscany 18:11:33k - sounds like a plan 18:11:38I will fix up VC6 and generate the makefiles... and oh well I may as well do the distro packagingtoo 18:11:47:) cool 18:12:12ok, I'll try to get a VC6 install on my machine, I only have vc8 now 18:12:36so we are using VC6 for this release right? 18:12:38well you should be able to run the command line with your VC7 I think 18:12:53jsdelfino - it would be good to try the command line build with vc8 18:13:09+1 for vc6 build only 18:13:17I mainly use VC 7 so I can test that if no one else does. 18:13:25vc8 doesn't work at all for now, SDOs don't run, throwing an incompatible list exception 18:13:28ok. I'll post on dev when I have a working VC6 and generated make 18:13:41great 18:13:56I'll try to get a VC6 install 18:14:04So what samples will we include in the distro? 18:14:05So the other things we should work on this week are docs and samples 18:14:14still quicker than me :) 18:14:17jsdelfino ... I don;t think you need VC6 18:14:57samples- Calculator, PythonCalculator, RubyCalculator, BigBank are all good at the moment 18:15:06not sure about SupplyChain 18:15:24I think that's good. Let's leave SupplyChain out for now 18:15:50RubyBank? jsdelfino - do you know the status of that one? 18:15:58How are we going to package the "optional" language extensions - Ruby, Pyhton 18:15:58yes, it's working 18:16:18can we add a simple HelloWorld? what do you think? 18:16:35Calulator is our HelloWo
[C++] M2 release IRC chat today
Hi All, We will be having an IRC chat to discuss items for the C++ M2 release today Tuesday, October 3rd, at 17:00 GMT, 18:00 BST, 10am PDT The chat takes place on the freenode IRC network, (use server irc.freenode.net), on channel #tuscany, and is scheduled to last one hour. Please join us! If you need an IRC client for windows, check out http://www.mirc.com, and http://www.mirc.com/links.html has some links to clients for other OS's. Cheers Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [C++] M2 Release
Pete Robbins wrote: I think we should find a time tomorrow. I'm fairly flexible. 6pm BST (5pm GMT, 10am Pacific) may fit best. On 02/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: Hi Pete, Thanks for the licence text stuff. Yep, an IRC chat & tracking items via Jiras would be cool. When would be a good time for a chat? For me, tomorrow 4 til 5pm BST or Wednesday 5 til 6pm are both free. Good for anyone else? Cheers Andy On 10/2/06, Pete Robbins <[EMAIL PROTECTED]> wrote: > Andy, > > I'll do the change to the new licence text (hopefully tomorrow). > Should we have an IRC chat to prioritise outstanding items and Jiras? Is is > good to raise Jiras for all the work items such as doc etc so we can track > what get checked in from now up to the release. If we are trying to close > down for a release we should only be checking in for items that we need for > the release. > > Cheers, > > > On 02/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: > > > > Hi All, > > > > I think it would be good if we could get our first release candidate > > cut by or during ApacheCon (which is next week!) - do people think > > that is possible? > > > > With this in mind I propose we concentrate on the higher priority > > stuff, which to my mind is documentation, samples, build requirements > > (licencing, build files, etc), the PHP extension and the support for a > > particular spec level. > > > > Do people agree with this? Is there some particular functionality/bug > > fix that should go in? > > > > Cheers > > > > Andy > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Pete > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] 10am PDT works for me. -- Jean-Sebastien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [C++] M2 Release
I think we should find a time tomorrow. I'm fairly flexible. 6pm BST (5pm GMT, 10am Pacific) may fit best. On 02/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: Hi Pete, Thanks for the licence text stuff. Yep, an IRC chat & tracking items via Jiras would be cool. When would be a good time for a chat? For me, tomorrow 4 til 5pm BST or Wednesday 5 til 6pm are both free. Good for anyone else? Cheers Andy On 10/2/06, Pete Robbins <[EMAIL PROTECTED]> wrote: > Andy, > > I'll do the change to the new licence text (hopefully tomorrow). > Should we have an IRC chat to prioritise outstanding items and Jiras? Is is > good to raise Jiras for all the work items such as doc etc so we can track > what get checked in from now up to the release. If we are trying to close > down for a release we should only be checking in for items that we need for > the release. > > Cheers, > > > On 02/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: > > > > Hi All, > > > > I think it would be good if we could get our first release candidate > > cut by or during ApacheCon (which is next week!) - do people think > > that is possible? > > > > With this in mind I propose we concentrate on the higher priority > > stuff, which to my mind is documentation, samples, build requirements > > (licencing, build files, etc), the PHP extension and the support for a > > particular spec level. > > > > Do people agree with this? Is there some particular functionality/bug > > fix that should go in? > > > > Cheers > > > > Andy > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Pete > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Pete
Re: [C++] M2 Release
Hi Pete, Thanks for the licence text stuff. Yep, an IRC chat & tracking items via Jiras would be cool. When would be a good time for a chat? For me, tomorrow 4 til 5pm BST or Wednesday 5 til 6pm are both free. Good for anyone else? Cheers Andy On 10/2/06, Pete Robbins <[EMAIL PROTECTED]> wrote: Andy, I'll do the change to the new licence text (hopefully tomorrow). Should we have an IRC chat to prioritise outstanding items and Jiras? Is is good to raise Jiras for all the work items such as doc etc so we can track what get checked in from now up to the release. If we are trying to close down for a release we should only be checking in for items that we need for the release. Cheers, On 02/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: > > Hi All, > > I think it would be good if we could get our first release candidate > cut by or during ApacheCon (which is next week!) - do people think > that is possible? > > With this in mind I propose we concentrate on the higher priority > stuff, which to my mind is documentation, samples, build requirements > (licencing, build files, etc), the PHP extension and the support for a > particular spec level. > > Do people agree with this? Is there some particular functionality/bug > fix that should go in? > > Cheers > > Andy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Pete - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [C++] M2 Release
Andy, I'll do the change to the new licence text (hopefully tomorrow). Should we have an IRC chat to prioritise outstanding items and Jiras? Is is good to raise Jiras for all the work items such as doc etc so we can track what get checked in from now up to the release. If we are trying to close down for a release we should only be checking in for items that we need for the release. Cheers, On 02/10/06, Andrew Borley <[EMAIL PROTECTED]> wrote: Hi All, I think it would be good if we could get our first release candidate cut by or during ApacheCon (which is next week!) - do people think that is possible? With this in mind I propose we concentrate on the higher priority stuff, which to my mind is documentation, samples, build requirements (licencing, build files, etc), the PHP extension and the support for a particular spec level. Do people agree with this? Is there some particular functionality/bug fix that should go in? Cheers Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Pete
Re: [C++] M2 Release
On 10/2/06, Andrew Borley <[EMAIL PROTECTED]> wrote: Hi All, I think it would be good if we could get our first release candidate cut by or during ApacheCon (which is next week!) - do people think that is possible? With this in mind I propose we concentrate on the higher priority stuff, which to my mind is documentation, samples, build requirements (licencing, build files, etc), the PHP extension and the support for a particular spec level. Do people agree with this? Is there some particular functionality/bug fix that should go in? Cheers Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Andy, sounds like the right thing to do to me. A couple of points... I've haven't got back to making the PHP extension as functional as the Ruby and Python extensions yet. The PHP SCA/SDO releases got in the way. But now PHP SCA is out we can use that as the basis for the PHP extension programming model. In theory its not a big deal but to do it properly will take a little thinking. So I'm not sure we can get it done this week:-( I'm currently looking at the details of the PHP SCA implementation so I'll report back when I know how it works. How did the interop stuff go? I lost track of it a little. Did someone offer to repeat your interop tests on the java side. Getting Java/C++ SCA interop the web service level would be cool as we go into milestone 2. When we tried with M! java their binding implementation didn't work for us but now thats been rewritten so would be good to feed back to java about whether it's good this time. S
[C++] M2 Release
Hi All, I think it would be good if we could get our first release candidate cut by or during ApacheCon (which is next week!) - do people think that is possible? With this in mind I propose we concentrate on the higher priority stuff, which to my mind is documentation, samples, build requirements (licencing, build files, etc), the PHP extension and the support for a particular spec level. Do people agree with this? Is there some particular functionality/bug fix that should go in? Cheers Andy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
