Hi all, I'd like to know where everyone stands on the CPP issues brought up during the VOTE thread. I am disappointed to see that it took a vote thread to bring up these issues. I know everyone is busy but we as a project need to get better at doing releases.
CPP Cluster problems: I'm surprised that this is coming up now. This is the 4 build that has been complete for testing. I would really have like to get feedback of this nature at a much earlier stage of the release process. What is the implication of this issue? Does it just mean you cannot build the cpp broker for cluster usage? I remember starting up the cpp broker from the built package so it at leasts built and ran. Is there anyone familiar with this code base that is prepared to put the time in to address this issue? If no-one has time to do this are we happy to release the cpp broker without cluster support? CPP Python Example Verification: Ok that was my fault I thought === was a comment. If there is desire and commitment to address the above cpp issue then I will address this problem. I don't think this issue on its own is sufficient to require the RC to be rebuilt as we can document on the release page that the diff should only show the license info. CPP Release Notes: This issue comes up every release, I thought I had adjusted the CPP file to be similar to the java/dotnet. The solution is to edit the CPP to make it generic like the java/dotnet release notes and point users to our jira/wiki. Until we have an automatable way of creating release notes then this sort of error is going to occur. Again I can do this if there is need to rebuild the RC but I don't think that this error on it's own is sufficient cause to rebuild the RC. Regards Martin -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
