You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Justin Ross <jr...@redhat.com> on 2011/02/14 16:08:53 UTC
0.10 release update - feature integration week
Hi, folks. Our schedule (appended below) calls for all major features to
be functionally complete and on trunk by the 16th, this Wednesday.
This means we are rapidly approaching the point where we make choices. If
something won't be ready in time, we need to kick it to the next release.
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.
I'll begin running the release scripts tomorrow in order to discover any
new issues for the alpha release.
Thanks,
Justin
---
0.10 feature and improvement jiras:
http://bit.ly/h3Q7Sk
0.10 schedule:
16 Feb
- Alpha
- Trunk remains open
- Feature integration ends
- The alpha release tests the release process after the
introduction of major features
2 Mar, 2 weeks later
- Beta
- Branch for release (trunk remains open)
- Release branch commits require approval
- Release manager produces outstanding bug report, triages bugs
16 Mar, 2 weeks later
- RC1
23 Mar, 1 week later
- RC2
30 Mar, 1 week later
- RC3
- Targeted release date
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Andrew Stitcher <as...@redhat.com>.
On Mon, 2011-02-14 at 10:08 -0500, Justin Ross wrote:
> Hi, folks. Our schedule (appended below) calls for all major features to
> be functionally complete and on trunk by the 16th, this Wednesday.
>
> This means we are rapidly approaching the point where we make choices. If
> something won't be ready in time, we need to kick it to the next release.
>
> 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.
I'd like to get the JCA work (QPID-3044) into 0.10. It isn't quite ready
for review/integration by the 16th but I'd expect that should happen
this week.
I'd be comfortable integrating it since it has pretty much no impact on
any other part of the tree as it is very self contained.
Andrew
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Carl Trieloff <cc...@redhat.com>.
On 02/16/2011 04:10 PM, Paul Colby wrote:
> 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 (?).
>
>
go for it, let's try get it in.
> 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).
>
0.9 is the dev release
Carl.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Justin Ross <jr...@redhat.com>.
On Thu, 17 Feb 2011, Paul Colby wrote:
> On Tue, Feb 15, 2011 at 2:08 AM, Justin Ross <jr...@redhat.com> 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
Re: 0.10 release update - feature integration week
Posted by Paul Colby <pa...@colby.id.au>.
On Tue, Feb 15, 2011 at 2:08 AM, Justin Ross <jr...@redhat.com> 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 :)
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).
paul.
>
> I'll begin running the release scripts tomorrow in order to discover any new
> issues for the alpha release.
>
> Thanks,
> Justin
>
> ---
>
> 0.10 feature and improvement jiras:
>
> http://bit.ly/h3Q7Sk
>
> 0.10 schedule:
>
> 16 Feb
>
> - Alpha
> - Trunk remains open
> - Feature integration ends
> - The alpha release tests the release process after the
> introduction of major features
>
> 2 Mar, 2 weeks later
>
> - Beta
> - Branch for release (trunk remains open)
> - Release branch commits require approval
> - Release manager produces outstanding bug report, triages bugs
>
> 16 Mar, 2 weeks later
>
> - RC1
>
> 23 Mar, 1 week later
>
> - RC2
>
> 30 Mar, 1 week later
>
> - RC3
> - Targeted release date
>
>
>
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Justin Ross <jr...@redhat.com>.
On Mon, 14 Feb 2011, Gordon Sim wrote:
> On 02/14/2011 03:08 PM, Justin Ross wrote:
>> Hi, folks. Our schedule (appended below) calls for all major features
>> to be functionally complete and on trunk by the 16th, this Wednesday.
>>
>> This means we are rapidly approaching the point where we make choices.
>> If something won't be ready in time, we need to kick it to the next
>> release.
>>
>> 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.
>
> I *may* miss Wed by a day or so for
> https://issues.apache.org/jira/browse/QPID-3015. I'm hoping to have it ready
> in time but would like to request a couple of days leeway just in case.
Okay, no worries. I'm primarily concerned about getting it in this week.
Justin
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Gordon Sim <gs...@redhat.com>.
On 02/14/2011 05:19 PM, Gordon Sim wrote:
> On 02/14/2011 03:08 PM, Justin Ross wrote:
>> Hi, folks. Our schedule (appended below) calls for all major features
>> to be functionally complete and on trunk by the 16th, this Wednesday.
>>
>> This means we are rapidly approaching the point where we make choices.
>> If something won't be ready in time, we need to kick it to the next
>> release.
>>
>> 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.
>
> I *may* miss Wed by a day or so for
> https://issues.apache.org/jira/browse/QPID-3015. I'm hoping to have it
> ready in time but would like to request a couple of days leeway just in
> case.
I did indeed overrun with that JIRA. There is a patch up for review now.
It only covers the c++ broker (though I've stubbed the methods on java
to avoid breaking the build). I didn't have enough knowledge of the java
broker just yet, but would be happy to contribute a patch post 0.10.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Justin Ross <jr...@redhat.com>.
On Mon, 14 Feb 2011, Andrew Kennedy wrote:
> On 14 Feb 2011, at 17:19, Gordon Sim wrote:
>> On 02/14/2011 03:08 PM, Justin Ross wrote:
>>> Hi, folks. Our schedule (appended below) calls for all major features
>>> to be functionally complete and on trunk by the 16th, this Wednesday.
>>>
>>> This means we are rapidly approaching the point where we make choices.
>>> If something won't be ready in time, we need to kick it to the next
>>> release.
>>>
>>> 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.
>>
>> I *may* miss Wed by a day or so for
>> https://issues.apache.org/jira/browse/QPID-3015. I'm hoping to have it
>> ready in time but would like to request a couple of days leeway just in
>> case.
>
> Ditto,
>
> The biggest feature I'm working on is 0-10 InVM. We're pushing hard to get
> the implementation included but, again, there may be a day or so's slippage,
> as the merge of code left untouched since October went slightly awry ;(
>
> So, I want to *really* make sure there are no regressions and everything is
> stable before it's committed. Definitely before EOW, though.
>
> I can't remember offhand, but I could look up the JIRAs if you need them,
> Justin?
>
> Andrew.
Thanks, Andrew. That all sounds excellent. I see the feature jira,
QPID-2814, and that's sufficient. Just post any high-level status updates
(if things change) to that jira.
Justin
> --
> -- andrew d kennedy ? do not fold, bend, spindle, or mutilate ;
> -- http://grkvlt.blogspot.com/ ? edinburgh : +44 7582 293 255 ;
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Andrew Kennedy <an...@gmail.com>.
On 14 Feb 2011, at 17:19, Gordon Sim wrote:
> On 02/14/2011 03:08 PM, Justin Ross wrote:
>> Hi, folks. Our schedule (appended below) calls for all major
>> features
>> to be functionally complete and on trunk by the 16th, this Wednesday.
>>
>> This means we are rapidly approaching the point where we make
>> choices.
>> If something won't be ready in time, we need to kick it to the next
>> release.
>>
>> 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.
>
> I *may* miss Wed by a day or so for https://issues.apache.org/jira/
> browse/QPID-3015. I'm hoping to have it ready in time but would
> like to request a couple of days leeway just in case.
Ditto,
The biggest feature I'm working on is 0-10 InVM. We're pushing hard
to get the implementation included but, again, there may be a day or
so's slippage, as the merge of code left untouched since October went
slightly awry ;(
So, I want to *really* make sure there are no regressions and
everything is stable before it's committed. Definitely before EOW,
though.
I can't remember offhand, but I could look up the JIRAs if you need
them, Justin?
Andrew.
--
-- andrew d kennedy ? do not fold, bend, spindle, or mutilate ;
-- http://grkvlt.blogspot.com/ ? edinburgh : +44 7582 293 255 ;
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Gordon Sim <gs...@redhat.com>.
On 02/14/2011 03:08 PM, Justin Ross wrote:
> Hi, folks. Our schedule (appended below) calls for all major features
> to be functionally complete and on trunk by the 16th, this Wednesday.
>
> This means we are rapidly approaching the point where we make choices.
> If something won't be ready in time, we need to kick it to the next
> release.
>
> 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.
I *may* miss Wed by a day or so for
https://issues.apache.org/jira/browse/QPID-3015. I'm hoping to have it
ready in time but would like to request a couple of days leeway just in
case.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: 0.10 release update - feature integration week
Posted by Steve Huston <sh...@riverace.com>.
To those interested...
The Windows Service changes won't be in for 0.10 - the submitter didn't
do many of the code changes I asked for and on a quick read I'm not
going to be able to beat this into shape in one day.
I'll keep plugging at it as time permits, but it won't be in 0.10.
-Steve
> -----Original Message-----
> From: Andrew Stitcher [mailto:astitcher@redhat.com]
> Sent: Thursday, February 17, 2011 2:45 PM
> To: dev@qpid.apache.org
> Subject: RE: 0.10 release update - feature integration week
>
>
> On Wed, 2011-02-16 at 18:04 -0500, Steve Huston wrote:
> > > Hi, Steve. End of the week is certainly okay.
> >
> > Ok, thanks.
> >
> > > I see that change introduces some (warning, speaking from
> > > some naivete
> > > here) big changes to broker config. If that's the case, I'd
> > > like it to
> > > get a shot at some extra review.
> >
> > It's in JIRA... Reviews are welcome. Some of my earlier
> review to the
> > submitter wasn't acted on, so there's real work to be done
> to get it
> > ready for inclusion. If my time is less free than I
> anticipate I may
> > not have time to get it in, but I'm going to try.
>
> Steve could you possibly publish the patch to review board?
> I'd like to review this change and I've found that review
> board is by far the most productive way to do it.
>
> Thanks
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: 0.10 release update - feature integration week
Posted by Steve Huston <sh...@riverace.com>.
> -----Original Message-----
> From: Andrew Stitcher [mailto:astitcher@redhat.com]
> Sent: Thursday, February 17, 2011 2:45 PM
> To: dev@qpid.apache.org
> Subject: RE: 0.10 release update - feature integration week
>
>
> On Wed, 2011-02-16 at 18:04 -0500, Steve Huston wrote:
> > > Hi, Steve. End of the week is certainly okay.
> >
> > Ok, thanks.
> >
> > > I see that change introduces some (warning, speaking from
> > > some naivete
> > > here) big changes to broker config. If that's the case, I'd
> > > like it to
> > > get a shot at some extra review.
> >
> > It's in JIRA... Reviews are welcome. Some of my earlier
> review to the
> > submitter wasn't acted on, so there's real work to be done
> to get it
> > ready for inclusion. If my time is less free than I
> anticipate I may
> > not have time to get it in, but I'm going to try.
>
> Steve could you possibly publish the patch to review board?
> I'd like to review this change and I've found that review
> board is by far the most productive way to do it.
The latest patch is attached to QPID-2519 and is also on Review Board (I
mentioned Andrew specifically, but all are welcome to comment).
Thanks,
-Steve
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: 0.10 release update - feature integration week
Posted by Steve Huston <sh...@riverace.com>.
Yes, if I can dig up the review board details and also get the patches
ready for such a review. No problem.
-Steve
> -----Original Message-----
> From: Andrew Stitcher [mailto:astitcher@redhat.com]
> Sent: Thursday, February 17, 2011 2:45 PM
> To: dev@qpid.apache.org
> Subject: RE: 0.10 release update - feature integration week
>
>
> On Wed, 2011-02-16 at 18:04 -0500, Steve Huston wrote:
> > > Hi, Steve. End of the week is certainly okay.
> >
> > Ok, thanks.
> >
> > > I see that change introduces some (warning, speaking from
> > > some naivete
> > > here) big changes to broker config. If that's the case, I'd
> > > like it to
> > > get a shot at some extra review.
> >
> > It's in JIRA... Reviews are welcome. Some of my earlier
> review to the
> > submitter wasn't acted on, so there's real work to be done
> to get it
> > ready for inclusion. If my time is less free than I
> anticipate I may
> > not have time to get it in, but I'm going to try.
>
> Steve could you possibly publish the patch to review board?
> I'd like to review this change and I've found that review
> board is by far the most productive way to do it.
>
> Thanks
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: 0.10 release update - feature integration week
Posted by Andrew Stitcher <as...@redhat.com>.
On Wed, 2011-02-16 at 18:04 -0500, Steve Huston wrote:
> > Hi, Steve. End of the week is certainly okay.
>
> Ok, thanks.
>
> > I see that change introduces some (warning, speaking from
> > some naivete
> > here) big changes to broker config. If that's the case, I'd
> > like it to
> > get a shot at some extra review.
>
> It's in JIRA... Reviews are welcome. Some of my earlier review to the
> submitter wasn't acted on, so there's real work to be done to get it
> ready for inclusion. If my time is less free than I anticipate I may not
> have time to get it in, but I'm going to try.
Steve could you possibly publish the patch to review board? I'd like to
review this change and I've found that review board is by far the most
productive way to do it.
Thanks
Andrew
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: 0.10 release update - feature integration week
Posted by Steve Huston <sh...@riverace.com>.
> Hi, Steve. End of the week is certainly okay.
Ok, thanks.
> I see that change introduces some (warning, speaking from
> some naivete
> here) big changes to broker config. If that's the case, I'd
> like it to
> get a shot at some extra review.
It's in JIRA... Reviews are welcome. Some of my earlier review to the
submitter wasn't acted on, so there's real work to be done to get it
ready for inclusion. If my time is less free than I anticipate I may not
have time to get it in, but I'm going to try.
-Steve
> On Wed, 16 Feb 2011, Steve Huston wrote:
>
> > Hi Justin,
> >
> > I'm going to try and get Kerry Bonin's QPID-2519 in, allowing the
> > broker to run as a service on Windows.
> >
> > Is it legit to get that in by the end of the week or no?
> >
> > -Steve
> >
> >> -----Original Message-----
> >> From: Justin Ross [mailto:jross@redhat.com]
> >> Sent: Monday, February 14, 2011 10:09 AM
> >> To: dev@qpid.apache.org
> >> Subject: 0.10 release update - feature integration week
> >>
> >>
> >> Hi, folks. Our schedule (appended below) calls for all major
> >> features to be functionally complete and on trunk by the
> 16th, this
> >> Wednesday.
> >>
> >> This means we are rapidly approaching the point where we make
> >> choices. If something won't be ready in time, we need to
> kick it to
> >> the next release.
> >>
> >> 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.
> >>
> >> I'll begin running the release scripts tomorrow in order
> to discover
> >> any new issues for the alpha release.
> >>
> >> Thanks,
> >> Justin
> >>
> >> ---
> >>
> >> 0.10 feature and improvement jiras:
> >>
> >> http://bit.ly/h3Q7Sk
> >>
> >> 0.10 schedule:
> >>
> >> 16 Feb
> >>
> >> - Alpha
> >> - Trunk remains open
> >> - Feature integration ends
> >> - The alpha release tests the release process after the
> >> introduction of major features
> >>
> >> 2 Mar, 2 weeks later
> >>
> >> - Beta
> >> - Branch for release (trunk remains open)
> >> - Release branch commits require approval
> >> - Release manager produces outstanding bug report,
> triages bugs
> >>
> >> 16 Mar, 2 weeks later
> >>
> >> - RC1
> >>
> >> 23 Mar, 1 week later
> >>
> >> - RC2
> >>
> >> 30 Mar, 1 week later
> >>
> >> - RC3
> >> - Targeted release date
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> Apache Qpid - AMQP Messaging Implementation
> >> Project: http://qpid.apache.org
> >> Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >>
> >>
> >
> >
> >
> ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: 0.10 release update - feature integration week
Posted by Justin Ross <jr...@redhat.com>.
Hi, Steve. End of the week is certainly okay.
I see that change introduces some (warning, speaking from some naivete
here) big changes to broker config. If that's the case, I'd like it to
get a shot at some extra review.
Justin
On Wed, 16 Feb 2011, Steve Huston wrote:
> Hi Justin,
>
> I'm going to try and get Kerry Bonin's QPID-2519 in, allowing the broker
> to run as a service on Windows.
>
> Is it legit to get that in by the end of the week or no?
>
> -Steve
>
>> -----Original Message-----
>> From: Justin Ross [mailto:jross@redhat.com]
>> Sent: Monday, February 14, 2011 10:09 AM
>> To: dev@qpid.apache.org
>> Subject: 0.10 release update - feature integration week
>>
>>
>> Hi, folks. Our schedule (appended below) calls for all major
>> features to
>> be functionally complete and on trunk by the 16th, this Wednesday.
>>
>> This means we are rapidly approaching the point where we make
>> choices. If
>> something won't be ready in time, we need to kick it to the
>> next release.
>>
>> 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.
>>
>> I'll begin running the release scripts tomorrow in order to
>> discover any
>> new issues for the alpha release.
>>
>> Thanks,
>> Justin
>>
>> ---
>>
>> 0.10 feature and improvement jiras:
>>
>> http://bit.ly/h3Q7Sk
>>
>> 0.10 schedule:
>>
>> 16 Feb
>>
>> - Alpha
>> - Trunk remains open
>> - Feature integration ends
>> - The alpha release tests the release process after the
>> introduction of major features
>>
>> 2 Mar, 2 weeks later
>>
>> - Beta
>> - Branch for release (trunk remains open)
>> - Release branch commits require approval
>> - Release manager produces outstanding bug report, triages bugs
>>
>> 16 Mar, 2 weeks later
>>
>> - RC1
>>
>> 23 Mar, 1 week later
>>
>> - RC2
>>
>> 30 Mar, 1 week later
>>
>> - RC3
>> - Targeted release date
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
RE: 0.10 release update - feature integration week
Posted by Steve Huston <sh...@riverace.com>.
Hi Justin,
I'm going to try and get Kerry Bonin's QPID-2519 in, allowing the broker
to run as a service on Windows.
Is it legit to get that in by the end of the week or no?
-Steve
> -----Original Message-----
> From: Justin Ross [mailto:jross@redhat.com]
> Sent: Monday, February 14, 2011 10:09 AM
> To: dev@qpid.apache.org
> Subject: 0.10 release update - feature integration week
>
>
> Hi, folks. Our schedule (appended below) calls for all major
> features to
> be functionally complete and on trunk by the 16th, this Wednesday.
>
> This means we are rapidly approaching the point where we make
> choices. If
> something won't be ready in time, we need to kick it to the
> next release.
>
> 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.
>
> I'll begin running the release scripts tomorrow in order to
> discover any
> new issues for the alpha release.
>
> Thanks,
> Justin
>
> ---
>
> 0.10 feature and improvement jiras:
>
> http://bit.ly/h3Q7Sk
>
> 0.10 schedule:
>
> 16 Feb
>
> - Alpha
> - Trunk remains open
> - Feature integration ends
> - The alpha release tests the release process after the
> introduction of major features
>
> 2 Mar, 2 weeks later
>
> - Beta
> - Branch for release (trunk remains open)
> - Release branch commits require approval
> - Release manager produces outstanding bug report, triages bugs
>
> 16 Mar, 2 weeks later
>
> - RC1
>
> 23 Mar, 1 week later
>
> - RC2
>
> 30 Mar, 1 week later
>
> - RC3
> - Targeted release date
>
>
>
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Ken Giusti <kg...@redhat.com>.
Fyi - attached a short doc describing the user interface for this feature.
https://issues.apache.org/jira/browse/QPID-2935
Feedback enthusiastically welcomed.
-K
----- Original Message -----
> I've just merged the QPID-2935 branch into trunk.
>
> I'll update the JIRA shortly, and attach some documentation describing
> the U.I. as it currently stands.
>
> Feedback/issues, etc - let me know. Thanks,
>
> -K
>
> ----- Original Message -----
> > Hi, Ken.
> >
> > I think the compromise you've struck with clustering is sensible
> > for the 0.10 release. If the work to make flow control work with
> > clustering is minor, we may be able to include it as a bug fix in
> > 0.10.
> > If, otoh, the work required is more extensive, we can address it in
> > 0.12.
> >
> > Either way, I think it's a "go".
> >
> > Justin
> >
> > On Thu, 17 Feb 2011, Ken Giusti wrote:
> >
> > > 10^6 apologies for not weighing in sooner...
> > >
> > > Regarding qpid-2935:
> > >
> > > Currently, standalone broker flow control is 'code complete' - it
> > > is
> > > passing a set of new unit tests I've added.
> > >
> > > I've run into some problems replicating state when using flow
> > > control in a clustered broker. Alan's is helping out here, but for
> > > now I've automatically disabled flow control when a broker is a
> > > member of a cluster.
> > >
> > > I've just resync'ed to trunk and refactored to use Gordon's "queue
> > > observer" api - all work is currently on branches/qpid-2935 - and
> > > "make check" looks good.
> > >
> > > Other than the cluster issue, I've got a couple of small cleanups,
> > > like verifying the cmake + windows build.
> > >
> > > Worst case, if we cannot get a solution in place for clustered
> > > brokers soon, would it be acceptable to allow 0.10 to support
> > > producer flow control for only for non-clustered brokers?
> > >
> > >
> > > -K
> > >
> > > ----- Original Message -----
> > >> Hi, folks. Our schedule (appended below) calls for all major
> > >> features
> > >> to
> > >> be functionally complete and on trunk by the 16th, this
> > >> Wednesday.
> > >>
> > >> This means we are rapidly approaching the point where we make
> > >> choices.
> > >> If
> > >> something won't be ready in time, we need to kick it to the next
> > >> release.
> > >>
> > >> 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.
> > >>
> > >> I'll begin running the release scripts tomorrow in order to
> > >> discover
> > >> any
> > >> new issues for the alpha release.
> > >>
> > >> Thanks,
> > >> Justin
> > >>
> > >> ---
> > >>
> > >> 0.10 feature and improvement jiras:
> > >>
> > >> http://bit.ly/h3Q7Sk
> > >>
> > >> 0.10 schedule:
> > >>
> > >> 16 Feb
> > >>
> > >> - Alpha
> > >> - Trunk remains open
> > >> - Feature integration ends
> > >> - The alpha release tests the release process after the
> > >> introduction of major features
> > >>
> > >> 2 Mar, 2 weeks later
> > >>
> > >> - Beta
> > >> - Branch for release (trunk remains open)
> > >> - Release branch commits require approval
> > >> - Release manager produces outstanding bug report, triages bugs
> > >>
> > >> 16 Mar, 2 weeks later
> > >>
> > >> - RC1
> > >>
> > >> 23 Mar, 1 week later
> > >>
> > >> - RC2
> > >>
> > >> 30 Mar, 1 week later
> > >>
> > >> - RC3
> > >> - Targeted release date
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> ---------------------------------------------------------------------
> > >> Apache Qpid - AMQP Messaging Implementation
> > >> Project: http://qpid.apache.org
> > >> Use/Interact: mailto:dev-subscribe@qpid.apache.org
> > >
> > > ---------------------------------------------------------------------
> > > Apache Qpid - AMQP Messaging Implementation
> > > Project: http://qpid.apache.org
> > > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Ken Giusti <kg...@redhat.com>.
I've just merged the QPID-2935 branch into trunk.
I'll update the JIRA shortly, and attach some documentation describing the U.I. as it currently stands.
Feedback/issues, etc - let me know. Thanks,
-K
----- Original Message -----
> Hi, Ken.
>
> I think the compromise you've struck with clustering is sensible
> for the 0.10 release. If the work to make flow control work with
> clustering is minor, we may be able to include it as a bug fix in
> 0.10.
> If, otoh, the work required is more extensive, we can address it in
> 0.12.
>
> Either way, I think it's a "go".
>
> Justin
>
> On Thu, 17 Feb 2011, Ken Giusti wrote:
>
> > 10^6 apologies for not weighing in sooner...
> >
> > Regarding qpid-2935:
> >
> > Currently, standalone broker flow control is 'code complete' - it is
> > passing a set of new unit tests I've added.
> >
> > I've run into some problems replicating state when using flow
> > control in a clustered broker. Alan's is helping out here, but for
> > now I've automatically disabled flow control when a broker is a
> > member of a cluster.
> >
> > I've just resync'ed to trunk and refactored to use Gordon's "queue
> > observer" api - all work is currently on branches/qpid-2935 - and
> > "make check" looks good.
> >
> > Other than the cluster issue, I've got a couple of small cleanups,
> > like verifying the cmake + windows build.
> >
> > Worst case, if we cannot get a solution in place for clustered
> > brokers soon, would it be acceptable to allow 0.10 to support
> > producer flow control for only for non-clustered brokers?
> >
> >
> > -K
> >
> > ----- Original Message -----
> >> Hi, folks. Our schedule (appended below) calls for all major
> >> features
> >> to
> >> be functionally complete and on trunk by the 16th, this Wednesday.
> >>
> >> This means we are rapidly approaching the point where we make
> >> choices.
> >> If
> >> something won't be ready in time, we need to kick it to the next
> >> release.
> >>
> >> 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.
> >>
> >> I'll begin running the release scripts tomorrow in order to
> >> discover
> >> any
> >> new issues for the alpha release.
> >>
> >> Thanks,
> >> Justin
> >>
> >> ---
> >>
> >> 0.10 feature and improvement jiras:
> >>
> >> http://bit.ly/h3Q7Sk
> >>
> >> 0.10 schedule:
> >>
> >> 16 Feb
> >>
> >> - Alpha
> >> - Trunk remains open
> >> - Feature integration ends
> >> - The alpha release tests the release process after the
> >> introduction of major features
> >>
> >> 2 Mar, 2 weeks later
> >>
> >> - Beta
> >> - Branch for release (trunk remains open)
> >> - Release branch commits require approval
> >> - Release manager produces outstanding bug report, triages bugs
> >>
> >> 16 Mar, 2 weeks later
> >>
> >> - RC1
> >>
> >> 23 Mar, 1 week later
> >>
> >> - RC2
> >>
> >> 30 Mar, 1 week later
> >>
> >> - RC3
> >> - Targeted release date
> >>
> >>
> >>
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> Apache Qpid - AMQP Messaging Implementation
> >> Project: http://qpid.apache.org
> >> Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project: http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Justin Ross <jr...@redhat.com>.
Hi, Ken.
I think the compromise you've struck with clustering is sensible
for the 0.10 release. If the work to make flow control work with
clustering is minor, we may be able to include it as a bug fix in 0.10.
If, otoh, the work required is more extensive, we can address it in 0.12.
Either way, I think it's a "go".
Justin
On Thu, 17 Feb 2011, Ken Giusti wrote:
> 10^6 apologies for not weighing in sooner...
>
> Regarding qpid-2935:
>
> Currently, standalone broker flow control is 'code complete' - it is passing a set of new unit tests I've added.
>
> I've run into some problems replicating state when using flow control in a clustered broker. Alan's is helping out here, but for now I've automatically disabled flow control when a broker is a member of a cluster.
>
> I've just resync'ed to trunk and refactored to use Gordon's "queue observer" api - all work is currently on branches/qpid-2935 - and "make check" looks good.
>
> Other than the cluster issue, I've got a couple of small cleanups, like verifying the cmake + windows build.
>
> Worst case, if we cannot get a solution in place for clustered brokers soon, would it be acceptable to allow 0.10 to support producer flow control for only for non-clustered brokers?
>
>
> -K
>
> ----- Original Message -----
>> Hi, folks. Our schedule (appended below) calls for all major features
>> to
>> be functionally complete and on trunk by the 16th, this Wednesday.
>>
>> This means we are rapidly approaching the point where we make choices.
>> If
>> something won't be ready in time, we need to kick it to the next
>> release.
>>
>> 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.
>>
>> I'll begin running the release scripts tomorrow in order to discover
>> any
>> new issues for the alpha release.
>>
>> Thanks,
>> Justin
>>
>> ---
>>
>> 0.10 feature and improvement jiras:
>>
>> http://bit.ly/h3Q7Sk
>>
>> 0.10 schedule:
>>
>> 16 Feb
>>
>> - Alpha
>> - Trunk remains open
>> - Feature integration ends
>> - The alpha release tests the release process after the
>> introduction of major features
>>
>> 2 Mar, 2 weeks later
>>
>> - Beta
>> - Branch for release (trunk remains open)
>> - Release branch commits require approval
>> - Release manager produces outstanding bug report, triages bugs
>>
>> 16 Mar, 2 weeks later
>>
>> - RC1
>>
>> 23 Mar, 1 week later
>>
>> - RC2
>>
>> 30 Mar, 1 week later
>>
>> - RC3
>> - Targeted release date
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project: http://qpid.apache.org
>> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
Re: 0.10 release update - feature integration week
Posted by Ken Giusti <kg...@redhat.com>.
10^6 apologies for not weighing in sooner...
Regarding qpid-2935:
Currently, standalone broker flow control is 'code complete' - it is passing a set of new unit tests I've added.
I've run into some problems replicating state when using flow control in a clustered broker. Alan's is helping out here, but for now I've automatically disabled flow control when a broker is a member of a cluster.
I've just resync'ed to trunk and refactored to use Gordon's "queue observer" api - all work is currently on branches/qpid-2935 - and "make check" looks good.
Other than the cluster issue, I've got a couple of small cleanups, like verifying the cmake + windows build.
Worst case, if we cannot get a solution in place for clustered brokers soon, would it be acceptable to allow 0.10 to support producer flow control for only for non-clustered brokers?
-K
----- Original Message -----
> Hi, folks. Our schedule (appended below) calls for all major features
> to
> be functionally complete and on trunk by the 16th, this Wednesday.
>
> This means we are rapidly approaching the point where we make choices.
> If
> something won't be ready in time, we need to kick it to the next
> release.
>
> 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.
>
> I'll begin running the release scripts tomorrow in order to discover
> any
> new issues for the alpha release.
>
> Thanks,
> Justin
>
> ---
>
> 0.10 feature and improvement jiras:
>
> http://bit.ly/h3Q7Sk
>
> 0.10 schedule:
>
> 16 Feb
>
> - Alpha
> - Trunk remains open
> - Feature integration ends
> - The alpha release tests the release process after the
> introduction of major features
>
> 2 Mar, 2 weeks later
>
> - Beta
> - Branch for release (trunk remains open)
> - Release branch commits require approval
> - Release manager produces outstanding bug report, triages bugs
>
> 16 Mar, 2 weeks later
>
> - RC1
>
> 23 Mar, 1 week later
>
> - RC2
>
> 30 Mar, 1 week later
>
> - RC3
> - Targeted release date
>
>
>
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project: http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org