No concerns from me, as mentioned elsewhere I was planning to ask the same (after getting my other vote finished :P) due to noticing earlier that Matt asked about the next release on IRC yesterday. Upon checking, it is ~4 months since the last branch, so things should have been getting underway by now.
My only question is whether we want to proceed with the relayout [1] work now, giving e.g. a qpid-cpp release containing the broker and tools, or instead leave that until after the release. I can see that it might be safest to get a release out now and then go about reorganising things (though we said the same thing last time around :D). The Java components have already been moved, so we should get round to doing the others. [1] https://cwiki.apache.org/confluence/display/qpid/Source+tree+layout+proposal On 11 June 2015 at 19:58, Gordon Sim <[email protected]> wrote: > There have been numerous fixes in qpid-cpp since the last release and it > would be nice to get a new release out. Anyone have any concerns about that > or anything pending they would like to land before we start the process? > > I'm thinking we can just release qpid-cpp on its own, unless there are fixes > in other components (qpid-python, qpid-tools) that people want to see > released? (I know qpid-java is planning its own release cycle now it has > moved) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
