You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Ted Ross <tr...@redhat.com> on 2017/03/22 13:43:42 UTC
Qpid Dispatch Release Plans
A couple of topics for discussion:
Qpid Dispatch Router 0.8.0 release
==================================
As of now, there are 116 resolved issues queued up for 0.8.0. I'd like
to wrap up this release in the next week. I plan to defer all of the
pending features to the next release.
If anyone has any bug fixes they would like to see included in this
release that are not already set to "Fix Version: 0.8.0", please put
them on the list.
Release Numbering
=================
I'd like to propose that the next release (after 0.8.0) be called 1.0.0.
The x.y.z release numbering would follow the normal expectations:
- All releases with the same 'x' shall be interoprable and we commit
to not breaking anyone's configurations as the project evolves
through a single major (x) version.
- Minor (y) releases shall be on a semi-regular cadence and shall
contain feature additions as well as rolled-up bug fixes.
- z releases shall be for bug fixes only and will be used as-needed.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid Dispatch Release Plans
Posted by Ken Giusti <kg...@redhat.com>.
----- Original Message -----
> From: "Ted Ross" <tr...@redhat.com>
> To: users@qpid.apache.org
> Sent: Wednesday, March 22, 2017 9:43:42 AM
> Subject: Qpid Dispatch Release Plans
>
> A couple of topics for discussion:
>
> Qpid Dispatch Router 0.8.0 release
> ==================================
>
> As of now, there are 116 resolved issues queued up for 0.8.0. I'd like
> to wrap up this release in the next week. I plan to defer all of the
> pending features to the next release.
>
> If anyone has any bug fixes they would like to see included in this
> release that are not already set to "Fix Version: 0.8.0", please put
> them on the list.
>
>
> Release Numbering
> =================
>
> I'd like to propose that the next release (after 0.8.0) be called 1.0.0.
>
> The x.y.z release numbering would follow the normal expectations:
>
> - All releases with the same 'x' shall be interoprable and we commit
> to not breaking anyone's configurations as the project evolves
> through a single major (x) version.
> - Minor (y) releases shall be on a semi-regular cadence and shall
> contain feature additions as well as rolled-up bug fixes.
> - z releases shall be for bug fixes only and will be used as-needed.
>
Will there be a policy for rolling upgrades? Rolling upgrade support is a pretty big deal - it's unlikely users will want to shutdown their entire dispatch network to cut from x.y.z -> x+1.y.z
Would it be possible to support major number rolling upgrades across one x release? In other words, support rolling upgrades from x.y.z -> x+1.y.z but not ->x+N.y.z where N > 1?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
--
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid Dispatch Release Plans
Posted by Ted Ross <tr...@redhat.com>.
On 03/27/2017 12:53 PM, Robbie Gemmell wrote:
> On 22 March 2017 at 13:43, Ted Ross <tr...@redhat.com> wrote:
>> A couple of topics for discussion:
>>
>> Qpid Dispatch Router 0.8.0 release
>> ==================================
>>
>> As of now, there are 116 resolved issues queued up for 0.8.0. I'd like to
>> wrap up this release in the next week. I plan to defer all of the pending
>> features to the next release.
>>
>
> Sounds good to me, theres been a lot of work since 0.7.0 that it would
> be great to see out in a release.
We've resolved all the planned issues. I'll build a release candidate
and start a vote here shortly.
>
>> If anyone has any bug fixes they would like to see included in this release
>> that are not already set to "Fix Version: 0.8.0", please put them on the
>> list.
>>
>>
>> Release Numbering
>> =================
>>
>> I'd like to propose that the next release (after 0.8.0) be called 1.0.0.
>>
>> The x.y.z release numbering would follow the normal expectations:
>>
>> - All releases with the same 'x' shall be interoprable and we commit
>> to not breaking anyone's configurations as the project evolves
>> through a single major (x) version.
>> - Minor (y) releases shall be on a semi-regular cadence and shall
>> contain feature additions as well as rolled-up bug fixes.
>> - z releases shall be for bug fixes only and will be used as-needed.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
>> For additional commands, e-mail: users-help@qpid.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid Dispatch Release Plans
Posted by Robbie Gemmell <ro...@gmail.com>.
On 22 March 2017 at 13:43, Ted Ross <tr...@redhat.com> wrote:
> A couple of topics for discussion:
>
> Qpid Dispatch Router 0.8.0 release
> ==================================
>
> As of now, there are 116 resolved issues queued up for 0.8.0. I'd like to
> wrap up this release in the next week. I plan to defer all of the pending
> features to the next release.
>
Sounds good to me, theres been a lot of work since 0.7.0 that it would
be great to see out in a release.
> If anyone has any bug fixes they would like to see included in this release
> that are not already set to "Fix Version: 0.8.0", please put them on the
> list.
>
>
> Release Numbering
> =================
>
> I'd like to propose that the next release (after 0.8.0) be called 1.0.0.
>
> The x.y.z release numbering would follow the normal expectations:
>
> - All releases with the same 'x' shall be interoprable and we commit
> to not breaking anyone's configurations as the project evolves
> through a single major (x) version.
> - Minor (y) releases shall be on a semi-regular cadence and shall
> contain feature additions as well as rolled-up bug fixes.
> - z releases shall be for bug fixes only and will be used as-needed.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid Dispatch Release Plans
Posted by Ted Ross <tr...@redhat.com>.
Those both look doable. I've flagged them for inclusion.
-Ted
On 03/22/2017 04:36 PM, Adel Boutros wrote:
> Hello Ted,
>
> What about:
> * DISPATCH-627
> * DISPATCH-624
>
> +1 for release model.
>
> Regards,
> Adel
>
> ________________________________
> From: Ted Ross <tr...@redhat.com>
> Sent: Wednesday, March 22, 2017 2:43:42 PM
> To: users@qpid.apache.org
> Subject: Qpid Dispatch Release Plans
>
> A couple of topics for discussion:
>
> Qpid Dispatch Router 0.8.0 release
> ==================================
>
> As of now, there are 116 resolved issues queued up for 0.8.0. I'd like
> to wrap up this release in the next week. I plan to defer all of the
> pending features to the next release.
>
> If anyone has any bug fixes they would like to see included in this
> release that are not already set to "Fix Version: 0.8.0", please put
> them on the list.
>
>
> Release Numbering
> =================
>
> I'd like to propose that the next release (after 0.8.0) be called 1.0.0.
>
> The x.y.z release numbering would follow the normal expectations:
>
> - All releases with the same 'x' shall be interoprable and we commit
> to not breaking anyone's configurations as the project evolves
> through a single major (x) version.
> - Minor (y) releases shall be on a semi-regular cadence and shall
> contain feature additions as well as rolled-up bug fixes.
> - z releases shall be for bug fixes only and will be used as-needed.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: Qpid Dispatch Release Plans
Posted by Adel Boutros <ad...@live.com>.
Hello Ted,
What about:
* DISPATCH-627
* DISPATCH-624
+1 for release model.
Regards,
Adel
________________________________
From: Ted Ross <tr...@redhat.com>
Sent: Wednesday, March 22, 2017 2:43:42 PM
To: users@qpid.apache.org
Subject: Qpid Dispatch Release Plans
A couple of topics for discussion:
Qpid Dispatch Router 0.8.0 release
==================================
As of now, there are 116 resolved issues queued up for 0.8.0. I'd like
to wrap up this release in the next week. I plan to defer all of the
pending features to the next release.
If anyone has any bug fixes they would like to see included in this
release that are not already set to "Fix Version: 0.8.0", please put
them on the list.
Release Numbering
=================
I'd like to propose that the next release (after 0.8.0) be called 1.0.0.
The x.y.z release numbering would follow the normal expectations:
- All releases with the same 'x' shall be interoprable and we commit
to not breaking anyone's configurations as the project evolves
through a single major (x) version.
- Minor (y) releases shall be on a semi-regular cadence and shall
contain feature additions as well as rolled-up bug fixes.
- z releases shall be for bug fixes only and will be used as-needed.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org