Re: 0.18 release update - upcoming dates
Hi Justin, on the Java Broker we're doing a fair amount of work on a new web-based management console which we want to have in for 0.18. We're currently doing this work on a branch that's tracking trunk. We *could* merge this to trunk now, but we prefer only to merge work which is fully completed and tested (the branch is pretty much alpha quality right now). Given that pretty much all the Java Broker developers are working on this, and the change is essentially orthogonal to the rest of the Java Broker... do you have any objections if we delay merging this down until closer to the July 2nd date? I think this actually decreases risk for the 0.18 release as by the time we merge down we'll be more confident that there's no showstoppers being put onto the trunk ahead of the 0.18 branch. Cheers, Rob On 12 June 2012 04:49, jr...@redhat.com wrote: Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 July We branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.18 release update - upcoming dates
Hi Justin, I would like to get the work I have done on the Qpid Java API implementation over the c++ client into trunk for the 0.18 release. This is a completely independent piece and would like to include as an experimental feature for the 0.18 release. I'm putting up the pieces for review as we speak. Depending on how the reviews go it may miss the alpha deadline. Therefore it would be great if I get a bit of flexibility in landing this work onto trunk. Regards, Rajith On Mon, Jun 18, 2012 at 6:27 AM, Rob Godfrey rob.j.godf...@gmail.com wrote: Hi Justin, on the Java Broker we're doing a fair amount of work on a new web-based management console which we want to have in for 0.18. We're currently doing this work on a branch that's tracking trunk. We *could* merge this to trunk now, but we prefer only to merge work which is fully completed and tested (the branch is pretty much alpha quality right now). Given that pretty much all the Java Broker developers are working on this, and the change is essentially orthogonal to the rest of the Java Broker... do you have any objections if we delay merging this down until closer to the July 2nd date? I think this actually decreases risk for the 0.18 release as by the time we merge down we'll be more confident that there's no showstoppers being put onto the trunk ahead of the 0.18 branch. Cheers, Rob On 12 June 2012 04:49, jr...@redhat.com wrote: Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 July We branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.18 release update - upcoming dates
Hi, Steve. Reading QPID-3914, it seems there are some questions about the patches' readiness. Do you think it's ready for inclusion? (If so, please indicate in the jira's comments so point and counterpoint are in one place.) As to timing in general, I'd be willing to accept a patch for this up to beta, provided we agree it should go in. Justin On Tue, 12 Jun 2012, Steve Huston wrote: I'd like to get the patch for QPID-3914 included. I should be able to get it in this week or next. -Steve On Jun 11, 2012, at 10:49 PM, jr...@redhat.com wrote: Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 JulyWe branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.18 release update - upcoming dates
Hi, Rob. I don't have any objections. Since I feel better if I ask at least one question: does the console branch contain any important changes to the broker model or its operation? If not, I consider it safe to include up to beta. Justin On Mon, 18 Jun 2012, Rob Godfrey wrote: Hi Justin, on the Java Broker we're doing a fair amount of work on a new web-based management console which we want to have in for 0.18. We're currently doing this work on a branch that's tracking trunk. We *could* merge this to trunk now, but we prefer only to merge work which is fully completed and tested (the branch is pretty much alpha quality right now). Given that pretty much all the Java Broker developers are working on this, and the change is essentially orthogonal to the rest of the Java Broker... do you have any objections if we delay merging this down until closer to the July 2nd date? I think this actually decreases risk for the 0.18 release as by the time we merge down we'll be more confident that there's no showstoppers being put onto the trunk ahead of the 0.18 branch. Cheers, Rob On 12 June 2012 04:49, jr...@redhat.com wrote: Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 July We branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.18 release update - upcoming dates
Justin, As agreed on the other thread, I agree with Rob that it's better to hold on to the work I'm doing until we get more discussion/review. Most of my work (barring the C++/JNI code) are going to be used for the future client work and it's best we take more time to settle that down. Since we were not going to release this and make it available only on an experimental basis, its best we wait until we branch for the 0.18 release. I could create a branch off the same rev that you use for the release and then apply this patch to make it available for people who would want to use it. (I anyways need to move it out of my current branch as the name itself has created some confusion). Regards, Rajith On Mon, Jun 18, 2012 at 1:27 PM, Justin Ross jr...@redhat.com wrote: Hi, Steve. Reading QPID-3914, it seems there are some questions about the patches' readiness. Do you think it's ready for inclusion? (If so, please indicate in the jira's comments so point and counterpoint are in one place.) As to timing in general, I'd be willing to accept a patch for this up to beta, provided we agree it should go in. Justin On Tue, 12 Jun 2012, Steve Huston wrote: I'd like to get the patch for QPID-3914 included. I should be able to get it in this week or next. -Steve On Jun 11, 2012, at 10:49 PM, jr...@redhat.com wrote: Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 July We branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.18 release update - upcoming dates
On 18 June 2012 19:34, Justin Ross jr...@redhat.com wrote: Hi, Rob. I don't have any objections. Since I feel better if I ask at least one question: does the console branch contain any important changes to the broker model or its operation? If not, I consider it safe to include up to beta. Nope - there's a few minor changes, but almost all of the new code is in a plugin (the new code is essentially making things available to the plugin). If we can get this in for 0.18 then we could potentially remove the Eclipse based JMX console from this release which would reduce the size of the whole release bundle quite considerably. -- Rob Justin On Mon, 18 Jun 2012, Rob Godfrey wrote: Hi Justin, on the Java Broker we're doing a fair amount of work on a new web-based management console which we want to have in for 0.18. We're currently doing this work on a branch that's tracking trunk. We *could* merge this to trunk now, but we prefer only to merge work which is fully completed and tested (the branch is pretty much alpha quality right now). Given that pretty much all the Java Broker developers are working on this, and the change is essentially orthogonal to the rest of the Java Broker... do you have any objections if we delay merging this down until closer to the July 2nd date? I think this actually decreases risk for the 0.18 release as by the time we merge down we'll be more confident that there's no showstoppers being put onto the trunk ahead of the 0.18 branch. Cheers, Rob On 12 June 2012 04:49, jr...@redhat.com wrote: Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 July We branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.18 release update - upcoming dates
Justin, Ted - I'd like to get this federation feature in for 0.18: https://issues.apache.org/jira/browse/QPID-4063 Proposed patch attached to the jira, thanks, -K - Original Message - Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 JulyWe branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.18 release update - upcoming dates
On 06/11/2012 10:49 PM, jr...@redhat.com wrote: Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 July We branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. The new HA work (QPID-3603) is basically done now, there are some loose ends to tie up. - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
Re: 0.18 release update - upcoming dates
I'd like to get the patch for QPID-3914 included. I should be able to get it in this week or next. -Steve On Jun 11, 2012, at 10:49 PM, jr...@redhat.com wrote: Hi, folks. The time for 0.18 alpha is rapidly approaching, and beta soon after. I've adjusted the dates to allow a little more time for development, since this warning comes rather late. 0.18 alpha, 18 June Deadline for major features and disruptive changes 0.18 beta, 2 JulyWe branch for release, and 0.19 opens Contact me if there's something you'd like to get in for 0.18, and we can figure out where it fits. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
