You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Bergquist, Brett" <BB...@canoga.com> on 2014/03/28 18:10:40 UTC
Why are some bugs not going to make it into 10.10.2.1 release
Just wondering as some of the bugs that I reported and have been fixed are not going to be in this release. Basically without these, the release is not useful to me at least and i will have to continue to build and patch myself.
Take these for example:
https://issues.apache.org/jira/browse/DERBY-5561?filter=-2
https://issues.apache.org/jira/browse/DERBY-5560?filter=-2
These appear marked to 10.9.2.2 but don’t appear to be included in this release.
Re: Why are some bugs not going to make it into 10.10.2.1 release
Posted by Rick Hillegas <ri...@oracle.com>.
On 3/28/14 10:59 AM, Bergquist, Brett wrote:
> Okay, I was trying to review the release notes and I guess I either have the wrong or picked the wrong link on the email. Where are the proposed release notes located? I searched the Wiki first and found
>
> http://svn.apache.org/viewvc/db/derby/code/branches/10.10/RELEASE-NOTES.html?revision=1582424&view=markup
Try the version at the head of the branch:
https://svn.apache.org/viewvc/db/derby/code/branches/10.10/RELEASE-NOTES.html?view=co
> Is that the correct place to look? I just looked now and do see that 5560 is included so I was mistaken on that one.
>
> I am more concerned in making sure a bug fix is include in the release or not and was only going by the release notes as to which bugs are included. Bugs that are not included are going to have to be patched by me in before I can use the release. Not a big deal but it makes it easier when I know which ones were not included. The first one marked as fixed in 10.9.2.2 lead me to believe it was not fixed in 10.9.1.0 and thus might not be in 10.10.2.0
I can see that that's confusing. I don't know what's going on. Would be
interested in your feedback on whether the bug is actually fixed in
10.10.2.0.
Thanks,
-Rick
> Thanks for your time Rick.
>
> On Mar 28, 2014, at 1:36 PM, Rick Hillegas<ri...@oracle.com> wrote:
>
>> On 3/28/14 10:10 AM, Bergquist, Brett wrote:
>>> Just wondering as some of the bugs that I reported and have been fixed are not going to be in this release. Basically without these, the release is not useful to me at least and i will have to continue to build and patch myself.
>>>
>>> Take these for example:
>>>
>>> https://issues.apache.org/jira/browse/DERBY-5561?filter=-2
>> Hi Brett,
>>
>> It appears to me that this bug was fixed as of revision 1334919 on
>> 2012-05-07. So the fix was included in the 10.9.1.0 release candidate,
>> which was created at revision 1344872 on 2012-05-31. So this fix should
>> be in 10.9.1.0, 10.10.1.1, and 10.10.2.0. If you observe that the bug
>> wasn't fixed in 10.10.1.1, then something has gone wrong. I don't know
>> why this bug doesn't appear in the release notes for 10.9.1.0.
>>> https://issues.apache.org/jira/browse/DERBY-5560?filter=-2
>> Your fix for this bug was checked into the 10.10 branch at revision
>> 1513274 on 2013-08-12 so it should be in 10.10.2.0. I do see this bug
>> listed as fixed in the release notes for 10.10.2.0.
>>
>> Hope this helps,
>> -Rick
>>> These appear marked to 10.9.2.2 but don’t appear to be included in this release.
>>>
>>>
>
Re: Why are some bugs not going to make it into 10.10.2.1 release
Posted by "Bergquist, Brett" <BB...@canoga.com>.
Okay, I was trying to review the release notes and I guess I either have the wrong or picked the wrong link on the email. Where are the proposed release notes located? I searched the Wiki first and found
http://svn.apache.org/viewvc/db/derby/code/branches/10.10/RELEASE-NOTES.html?revision=1582424&view=markup
Is that the correct place to look? I just looked now and do see that 5560 is included so I was mistaken on that one.
I am more concerned in making sure a bug fix is include in the release or not and was only going by the release notes as to which bugs are included. Bugs that are not included are going to have to be patched by me in before I can use the release. Not a big deal but it makes it easier when I know which ones were not included. The first one marked as fixed in 10.9.2.2 lead me to believe it was not fixed in 10.9.1.0 and thus might not be in 10.10.2.0
Thanks for your time Rick.
On Mar 28, 2014, at 1:36 PM, Rick Hillegas <ri...@oracle.com> wrote:
> On 3/28/14 10:10 AM, Bergquist, Brett wrote:
>> Just wondering as some of the bugs that I reported and have been fixed are not going to be in this release. Basically without these, the release is not useful to me at least and i will have to continue to build and patch myself.
>>
>> Take these for example:
>>
>> https://issues.apache.org/jira/browse/DERBY-5561?filter=-2
> Hi Brett,
>
> It appears to me that this bug was fixed as of revision 1334919 on
> 2012-05-07. So the fix was included in the 10.9.1.0 release candidate,
> which was created at revision 1344872 on 2012-05-31. So this fix should
> be in 10.9.1.0, 10.10.1.1, and 10.10.2.0. If you observe that the bug
> wasn't fixed in 10.10.1.1, then something has gone wrong. I don't know
> why this bug doesn't appear in the release notes for 10.9.1.0.
>> https://issues.apache.org/jira/browse/DERBY-5560?filter=-2
> Your fix for this bug was checked into the 10.10 branch at revision
> 1513274 on 2013-08-12 so it should be in 10.10.2.0. I do see this bug
> listed as fixed in the release notes for 10.10.2.0.
>
> Hope this helps,
> -Rick
>> These appear marked to 10.9.2.2 but don’t appear to be included in this release.
>>
>>
>
Re: Why are some bugs not going to make it into 10.10.2.1 release
Posted by Rick Hillegas <ri...@oracle.com>.
On 3/28/14 10:10 AM, Bergquist, Brett wrote:
> Just wondering as some of the bugs that I reported and have been fixed are not going to be in this release. Basically without these, the release is not useful to me at least and i will have to continue to build and patch myself.
>
> Take these for example:
>
> https://issues.apache.org/jira/browse/DERBY-5561?filter=-2
Hi Brett,
It appears to me that this bug was fixed as of revision 1334919 on
2012-05-07. So the fix was included in the 10.9.1.0 release candidate,
which was created at revision 1344872 on 2012-05-31. So this fix should
be in 10.9.1.0, 10.10.1.1, and 10.10.2.0. If you observe that the bug
wasn't fixed in 10.10.1.1, then something has gone wrong. I don't know
why this bug doesn't appear in the release notes for 10.9.1.0.
> https://issues.apache.org/jira/browse/DERBY-5560?filter=-2
Your fix for this bug was checked into the 10.10 branch at revision
1513274 on 2013-08-12 so it should be in 10.10.2.0. I do see this bug
listed as fixed in the release notes for 10.10.2.0.
Hope this helps,
-Rick
> These appear marked to 10.9.2.2 but don’t appear to be included in this release.
>
>