You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@qpid.apache.org by Gordon Sim <gs...@redhat.com> on 2015/06/11 20:58:50 UTC
qpid-cpp release?
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: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp release?
Posted by Robbie Gemmell <ro...@gmail.com>.
On 16 June 2015 at 10:05, Gordon Sim <gs...@redhat.com> wrote:
> On 06/15/2015 04:57 PM, Robbie Gemmell wrote:
>>
>> I have added a qpid-cpp-0.34 version in JIRA that we can start
>> updating issues included in the release to use (we can then tidy up
>> issues for non-cpp changes assigned to the existing 0.33 and 33
>> versions).
>
>
> fyi: I think I've moved all the issues resolved in this release to use that
> new version.
>
Excellent, thanks Gordon.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp release?
Posted by Gordon Sim <gs...@redhat.com>.
On 06/15/2015 04:57 PM, Robbie Gemmell wrote:
> I have added a qpid-cpp-0.34 version in JIRA that we can start
> updating issues included in the release to use (we can then tidy up
> issues for non-cpp changes assigned to the existing 0.33 and 33
> versions).
fyi: I think I've moved all the issues resolved in this release to use
that new version.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp release?
Posted by Robbie Gemmell <ro...@gmail.com>.
I have added a qpid-cpp-0.34 version in JIRA that we can start
updating issues included in the release to use (we can then tidy up
issues for non-cpp changes assigned to the existing 0.33 and 33
versions).
On 15 June 2015 at 15:28, Robbie Gemmell <ro...@gmail.com> wrote:
> Thanks Chuck. I had a look at a some of the below late last week but
> I'll be following a somewhat simpler bespoke process for this cpp
> release, Justin can restore order when he returns.
>
> Robbie
>
> On 15 June 2015 at 14:12, Chuck Rolke <cr...@redhat.com> wrote:
>> Justin has notes on the process.
>>
>> Release process steps and notes
>>
>> https://drive.google.com/open?id=1ML8twg28315eSyVmn-Qo455Gr6mlxrQl05Wg-otawpE
>>
>> Release history
>>
>> https://drive.google.com/open?id=1HC916R-9Tbg9X2boOYBH6XroiXoQZwnJXwCm7Y5C99A
>>
>> Recent release pages - For finding out how it was done before
>>
>> https://cwiki.apache.org/confluence/display/qpid/0.32+Release
>> https://cwiki.apache.org/confluence/display/qpid/0.30+Release
>> https://cwiki.apache.org/confluence/display/qpid/0.28+Release
>>
>> Quirk - The tool Justin uses to generate the releases
>>
>> http://www.ssorj.net/projects/quirk.html
>>
>> Qpid site code - For updating the website for new releases; see the "Generating release content" section
>>
>> http://svn.apache.org/repos/asf/qpid/site/README
>>
>> ----- Original Message -----
>>> From: "Gordon Sim" <gs...@redhat.com>
>>> To: users@qpid.apache.org
>>> Sent: Friday, June 12, 2015 11:37:16 AM
>>> Subject: Re: qpid-cpp release?
>>>
>>> On 06/12/2015 04:13 PM, Robbie Gemmell wrote:
>>> > On 12 June 2015 at 10:50, Gordon Sim <gs...@redhat.com> wrote:
>>> >> On 06/12/2015 10:31 AM, Robbie Gemmell wrote:
>>> >>>
>>> >>> Some other things that have come to mind:
>>> >>>
>>> >>> - What is the version going to be, 33.0 ?
>>> >>
>>> >>
>>> >> Personally I'd be inclined to just stick with the existing convention,
>>> >> i.e.
>>> >> 0.34. However I'm not too bothered about the version number, so whatever
>>> >> gets the most support is fine with me.
>>> >>
>>> >
>>> > In the interests of getting something out promptly, lets just go with
>>> > 0.34 and use the current cpp dir contents, giving a ''qpid-cpp-0.34'
>>> >
>>> > I will spin an alpha today from trunk. We can create a branch later if
>>> > needed, but I'd e happy to just tag from trunk if noone is actually
>>> > planning any commits deemed unsuitable for the release.
>>>
>>> Sounds good! Thanks Robbie!
>>>
>>>
>>> ---------------------------------------------------------------------
>>> 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-cpp release?
Posted by Robbie Gemmell <ro...@gmail.com>.
Thanks Chuck. I had a look at a some of the below late last week but
I'll be following a somewhat simpler bespoke process for this cpp
release, Justin can restore order when he returns.
Robbie
On 15 June 2015 at 14:12, Chuck Rolke <cr...@redhat.com> wrote:
> Justin has notes on the process.
>
> Release process steps and notes
>
> https://drive.google.com/open?id=1ML8twg28315eSyVmn-Qo455Gr6mlxrQl05Wg-otawpE
>
> Release history
>
> https://drive.google.com/open?id=1HC916R-9Tbg9X2boOYBH6XroiXoQZwnJXwCm7Y5C99A
>
> Recent release pages - For finding out how it was done before
>
> https://cwiki.apache.org/confluence/display/qpid/0.32+Release
> https://cwiki.apache.org/confluence/display/qpid/0.30+Release
> https://cwiki.apache.org/confluence/display/qpid/0.28+Release
>
> Quirk - The tool Justin uses to generate the releases
>
> http://www.ssorj.net/projects/quirk.html
>
> Qpid site code - For updating the website for new releases; see the "Generating release content" section
>
> http://svn.apache.org/repos/asf/qpid/site/README
>
> ----- Original Message -----
>> From: "Gordon Sim" <gs...@redhat.com>
>> To: users@qpid.apache.org
>> Sent: Friday, June 12, 2015 11:37:16 AM
>> Subject: Re: qpid-cpp release?
>>
>> On 06/12/2015 04:13 PM, Robbie Gemmell wrote:
>> > On 12 June 2015 at 10:50, Gordon Sim <gs...@redhat.com> wrote:
>> >> On 06/12/2015 10:31 AM, Robbie Gemmell wrote:
>> >>>
>> >>> Some other things that have come to mind:
>> >>>
>> >>> - What is the version going to be, 33.0 ?
>> >>
>> >>
>> >> Personally I'd be inclined to just stick with the existing convention,
>> >> i.e.
>> >> 0.34. However I'm not too bothered about the version number, so whatever
>> >> gets the most support is fine with me.
>> >>
>> >
>> > In the interests of getting something out promptly, lets just go with
>> > 0.34 and use the current cpp dir contents, giving a ''qpid-cpp-0.34'
>> >
>> > I will spin an alpha today from trunk. We can create a branch later if
>> > needed, but I'd e happy to just tag from trunk if noone is actually
>> > planning any commits deemed unsuitable for the release.
>>
>> Sounds good! Thanks Robbie!
>>
>>
>> ---------------------------------------------------------------------
>> 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-cpp release?
Posted by Chuck Rolke <cr...@redhat.com>.
Justin has notes on the process.
Release process steps and notes
https://drive.google.com/open?id=1ML8twg28315eSyVmn-Qo455Gr6mlxrQl05Wg-otawpE
Release history
https://drive.google.com/open?id=1HC916R-9Tbg9X2boOYBH6XroiXoQZwnJXwCm7Y5C99A
Recent release pages - For finding out how it was done before
https://cwiki.apache.org/confluence/display/qpid/0.32+Release
https://cwiki.apache.org/confluence/display/qpid/0.30+Release
https://cwiki.apache.org/confluence/display/qpid/0.28+Release
Quirk - The tool Justin uses to generate the releases
http://www.ssorj.net/projects/quirk.html
Qpid site code - For updating the website for new releases; see the "Generating release content" section
http://svn.apache.org/repos/asf/qpid/site/README
----- Original Message -----
> From: "Gordon Sim" <gs...@redhat.com>
> To: users@qpid.apache.org
> Sent: Friday, June 12, 2015 11:37:16 AM
> Subject: Re: qpid-cpp release?
>
> On 06/12/2015 04:13 PM, Robbie Gemmell wrote:
> > On 12 June 2015 at 10:50, Gordon Sim <gs...@redhat.com> wrote:
> >> On 06/12/2015 10:31 AM, Robbie Gemmell wrote:
> >>>
> >>> Some other things that have come to mind:
> >>>
> >>> - What is the version going to be, 33.0 ?
> >>
> >>
> >> Personally I'd be inclined to just stick with the existing convention,
> >> i.e.
> >> 0.34. However I'm not too bothered about the version number, so whatever
> >> gets the most support is fine with me.
> >>
> >
> > In the interests of getting something out promptly, lets just go with
> > 0.34 and use the current cpp dir contents, giving a ''qpid-cpp-0.34'
> >
> > I will spin an alpha today from trunk. We can create a branch later if
> > needed, but I'd e happy to just tag from trunk if noone is actually
> > planning any commits deemed unsuitable for the release.
>
> Sounds good! Thanks Robbie!
>
>
> ---------------------------------------------------------------------
> 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-cpp release?
Posted by Gordon Sim <gs...@redhat.com>.
On 06/12/2015 04:13 PM, Robbie Gemmell wrote:
> On 12 June 2015 at 10:50, Gordon Sim <gs...@redhat.com> wrote:
>> On 06/12/2015 10:31 AM, Robbie Gemmell wrote:
>>>
>>> Some other things that have come to mind:
>>>
>>> - What is the version going to be, 33.0 ?
>>
>>
>> Personally I'd be inclined to just stick with the existing convention, i.e.
>> 0.34. However I'm not too bothered about the version number, so whatever
>> gets the most support is fine with me.
>>
>
> In the interests of getting something out promptly, lets just go with
> 0.34 and use the current cpp dir contents, giving a ''qpid-cpp-0.34'
>
> I will spin an alpha today from trunk. We can create a branch later if
> needed, but I'd e happy to just tag from trunk if noone is actually
> planning any commits deemed unsuitable for the release.
Sounds good! Thanks Robbie!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp release?
Posted by Robbie Gemmell <ro...@gmail.com>.
On 12 June 2015 at 10:50, Gordon Sim <gs...@redhat.com> wrote:
> On 06/12/2015 10:31 AM, Robbie Gemmell wrote:
>>
>> Some other things that have come to mind:
>>
>> - What is the version going to be, 33.0 ?
>
>
> Personally I'd be inclined to just stick with the existing convention, i.e.
> 0.34. However I'm not too bothered about the version number, so whatever
> gets the most support is fine with me.
>
In the interests of getting something out promptly, lets just go with
0.34 and use the current cpp dir contents, giving a ''qpid-cpp-0.34'
I will spin an alpha today from trunk. We can create a branch later if
needed, but I'd e happy to just tag from trunk if noone is actually
planning any commits deemed unsuitable for the release.
>> - JIRAs will likely need updated to appropriately segregate the 'Qpid
>> CPP' changes to their own version.
>> - The website will need a fair bit of surgery. The scripting used for
>> the site to generate the release pages, and the component pages,
>> doc+download pages, adding the menus etc mostly assumes everything is
>> being released currently. There is probably some 'fun' lurking in
>> there with all the JIRA links too (use of fix versions and
>> components).
>
>
>
> ---------------------------------------------------------------------
> 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-cpp release?
Posted by Gordon Sim <gs...@redhat.com>.
On 06/12/2015 10:31 AM, Robbie Gemmell wrote:
> Some other things that have come to mind:
>
> - What is the version going to be, 33.0 ?
Personally I'd be inclined to just stick with the existing convention,
i.e. 0.34. However I'm not too bothered about the version number, so
whatever gets the most support is fine with me.
> - JIRAs will likely need updated to appropriately segregate the 'Qpid
> CPP' changes to their own version.
> - The website will need a fair bit of surgery. The scripting used for
> the site to generate the release pages, and the component pages,
> doc+download pages, adding the menus etc mostly assumes everything is
> being released currently. There is probably some 'fun' lurking in
> there with all the JIRA links too (use of fix versions and
> components).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org
Re: qpid-cpp release?
Posted by Robbie Gemmell <ro...@gmail.com>.
Some other things that have come to mind:
- What is the version going to be, 33.0 ?
- JIRAs will likely need updated to appropriately segregate the 'Qpid
CPP' changes to their own version.
- The website will need a fair bit of surgery. The scripting used for
the site to generate the release pages, and the component pages,
doc+download pages, adding the menus etc mostly assumes everything is
being released currently. There is probably some 'fun' lurking in
there with all the JIRA links too (use of fix versions and
components).
Robbie
On 11 June 2015 at 20:08, Robbie Gemmell <ro...@gmail.com> wrote:
> 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 <gs...@redhat.com> 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: 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-cpp release?
Posted by Robbie Gemmell <ro...@gmail.com>.
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 <gs...@redhat.com> 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: 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