: Re: candidate commits for 0.9.1
On 04/29/2015 05:38 PM, Gordon Sim wrote:
On 04/27/2015 01:45 PM, Gordon Sim wrote:
On 04/27/2015 01:14 PM, Rafael Schloming wrote:
I also added PROTON-858 as a release blocker.
I've been trying to get a fix proposal together for that. I'll post
On 04/29/2015 05:38 PM, Gordon Sim wrote:
On 04/27/2015 01:45 PM, Gordon Sim wrote:
On 04/27/2015 01:14 PM, Rafael Schloming wrote:
I also added PROTON-858 as a release blocker.
I've been trying to get a fix proposal together for that. I'll post it
for review as soon as I'm reasonably
: Gordon Sim g...@redhat.com
To: proton@qpid.apache.org
Sent: Friday, May 1, 2015 6:02:09 AM
Subject: Re: candidate commits for 0.9.1
On 04/29/2015 05:38 PM, Gordon Sim wrote:
On 04/27/2015 01:45 PM, Gordon Sim wrote:
On 04/27/2015 01:14 PM, Rafael Schloming wrote:
I also added PROTON-858
On Wed, Apr 29, 2015 at 6:16 AM, Dominic Evans dominic.ev...@uk.ibm.com
wrote:
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
There were some changes on master and the branch yesterday, so I have
updated the commit lists again. The current categorised list of
commits is now at:
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
There were some changes on master and the branch yesterday, so I have
updated the commit lists again. The current categorised list of
commits is now at:
http://people.apache.org/~robbie/qpid/proton/0.9.1/git-cherry-pass3-c
There were some changes on master and the branch yesterday, so I have
updated the commit lists again. The current categorised list of
commits is now at:
http://people.apache.org/~robbie/qpid/proton/0.9.1/git-cherry-pass3-categorised.txt
As before, only the commits at the very bottom have been
On 29 April 2015 at 17:38, Gordon Sim g...@redhat.com wrote:
On 04/27/2015 01:45 PM, Gordon Sim wrote:
On 04/27/2015 01:14 PM, Rafael Schloming wrote:
I also added PROTON-858 as a release blocker.
I've been trying to get a fix proposal together for that. I'll post it
for review as soon as
On 04/27/2015 01:45 PM, Gordon Sim wrote:
On 04/27/2015 01:14 PM, Rafael Schloming wrote:
I also added PROTON-858 as a release blocker.
I've been trying to get a fix proposal together for that. I'll post it
for review as soon as I'm reasonably confident, still seeing some issues
at present
On 04/29/2015 07:15 PM, Rafael Schloming wrote:
On Wed, Apr 29, 2015 at 12:38 PM, Gordon Sim g...@redhat.com wrote:
On 04/27/2015 01:45 PM, Gordon Sim wrote:
On 04/27/2015 01:14 PM, Rafael Schloming wrote:
I also added PROTON-858 as a release blocker.
I've been trying to get a fix
On Wed, Apr 29, 2015 at 12:38 PM, Gordon Sim g...@redhat.com wrote:
On 04/27/2015 01:45 PM, Gordon Sim wrote:
On 04/27/2015 01:14 PM, Rafael Schloming wrote:
I also added PROTON-858 as a release blocker.
I've been trying to get a fix proposal together for that. I'll post it
for review as
On 04/27/2015 01:14 PM, Rafael Schloming wrote:
I also added PROTON-858 as a release blocker.
I've been trying to get a fix proposal together for that. I'll post it
for review as soon as I'm reasonably confident, still seeing some issues
at present (not 100% sure they are related, but am
On 27 April 2015 at 13:44, Robbie Gemmell robbie.gemm...@gmail.com wrote:
On 27 April 2015 at 13:23, Dominic Evans dominic.ev...@uk.ibm.com wrote:
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
I have gone through the git cherry output and categorised the
remaining commits from
I have gone through the git cherry output and categorised the
remaining commits from master that dont have a direct equivalent on
the 0.9.x branch, splitting according to what they update i.e. mainly
by language. I listed some as excluded based on what they are for, e.g
the 0.10 sasl work, and any
On 27 April 2015 at 13:14, Rafael Schloming r...@alum.mit.edu wrote:
This one should definitely go in:
Ok, I'll pick it in.
+ aa5ea2b62fd5680bc2a36bee14f72e037d8cc276 close the transport when the
selector reports an error
I also added PROTON-858 as a release blocker.
--Rafael
On Mon,
On 04/27/2015 12:46 PM, Robbie Gemmell wrote:
I have gone through the git cherry output and categorised the
remaining commits from master that dont have a direct equivalent on
the 0.9.x branch, splitting according to what they update i.e. mainly
by language. I listed some as excluded based on
This one should definitely go in:
+ aa5ea2b62fd5680bc2a36bee14f72e037d8cc276 close the transport when the
selector reports an error
I also added PROTON-858 as a release blocker.
--Rafael
On Mon, Apr 27, 2015 at 8:07 AM, Gordon Sim g...@redhat.com wrote:
On 04/27/2015 12:46 PM, Robbie
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
I have gone through the git cherry output and categorised the
remaining commits from master that dont have a direct equivalent on
the 0.9.x branch, splitting according to what they update i.e. mainly
by language. I listed some as
On 27 April 2015 at 13:07, Gordon Sim g...@redhat.com wrote:
On 04/27/2015 12:46 PM, Robbie Gemmell wrote:
I have gone through the git cherry output and categorised the
remaining commits from master that dont have a direct equivalent on
the 0.9.x branch, splitting according to what they
On 27 April 2015 at 13:23, Dominic Evans dominic.ev...@uk.ibm.com wrote:
-Robbie Gemmell robbie.gemm...@gmail.com wrote: -
I have gone through the git cherry output and categorised the
remaining commits from master that dont have a direct equivalent on
the 0.9.x branch, splitting
Ok I have now cherry picked the commits mentioned earlier by Gordon,
Rafael, and Dominic.
The current categorised list of commits is now at:
http://people.apache.org/~robbie/qpid/proton/0.9.1/git-cherry-pass2-categorised.txt
The bare git cherry -v 0.9.x master output is at:
New 0.9.x branch created, against the actual 0.9 tag this time. I have
updated the JIRAs for the all the commits included so far to add the
0.9.1 fix version. If you want any commits included, either git
cherry-pick -x them to the branch yourself or reply with the SHAs.
Output of git cherry -v
Ok ignore all that for now. Andrew has noted a problem with the branch.
I seemingly had a stale set of tags and an old 0.9 branch, so when I
thought I was branching from the 0.9 tag I was actually not, but
rather the 0.9-rc3 tag (which in my case happened to be the same as
0.9, but in an up to
I branched 0.9.x from the 0.9 tag and cherry picked the commits I
mentioned earlier. I have added a 0.9.1 version in JIRA, though I
havent yet updated the JIRAs for the commits which had one, I'll get
that over the weekend.
Here is an updated output from git-cherry of master agaisnt 0.9.x, for
23 matches
Mail list logo
