On Thu, 17 Feb 2011, Paul Colby wrote:
On Tue, Feb 15, 2011 at 2:08 AM, Justin Ross <[email protected]> wrote:
Hi, folks. Our schedule (appended below) calls for all major features to be
functionally complete and on trunk by the 16th, this Wednesday.
I'd love to be able to get my PHP binding into the next release... but
its not quite complete yet (very, very close).
We can make exceptions for changes that don't threaten to destabilize the
release. If you'd like an exception, it's quite important that we discuss
it now.
So I'd like an exception then :) The PHP binding certainly won't
destabilize anything.
But if it makes more sense to put the PHP binding off to a later
release to give it time to mature / prove, then that's fine with me ;)
As it is, I expect it to be "complete" sometime next week (though I'm
not sure how much is involved in implementing automake support (?).
Thanks :)
Hi, Paul. I agree, a new binding, provided it's isolated, is not a danger
to the release. That means you have more time, until we branch for beta.
I'd like to hear others' comments, but I tend to think we should adopt
things like this under some kind of preview status so that we can
carefully communicate about API stability and support.
BTW, what happened to a 0.9 release? Are odd point releases being
used for dev-only, or was 0.9 skipped for some reason (eg syncing with
AMQP standard versioning?), or is 0.9 still in progress are you guys
are just looking even further ahead to 0.10? (just curious).
We use linux kernel-esque numbering, meaning 0.9 is dev only. 0.9 turns
into 0.10 upon release.
Justin
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
