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 Myrna van Lunteren <m....@gmail.com> on 2011/06/20 20:48:24 UTC

backports for 10.8.2...

Hi,

I (wearing the release manager hat) have tentatively scheduled a bug
fix release off the 10.8 branch for mid-September.

I've been looking a little at the commits, and it seems to me that a
fair number of bug fixes have gone in to trunk already that haven't
been backported to 10.8.

Here's a list of revisions (with bug numbers) that I think haven't
been backported, and the committer.
Please look over this list, and if you can, backport any issues that
are not new features and would cause no incompatibility from trunk to
10.8.

If you think the revisions are ok to be backported, but you have no
time to do the backport yourself, please let me know, and I'll work on
it in the next couple of weeks.
If I listed revisions that are ok to be backported, but they aren't,
or I've listed them as not to be backported, but they are, also let me
know.
I would especially like input on those with ? (question marks).

I'll send out another email in August, and discuss items committed during July.

Myrna

revision      bug#     backport ok     committer
-----------------------------------------------------------------------
http://svn.apache.org/viewvc?view=revision&revision=1096361 no-JIRA yes mamta
http://svn.apache.org/viewvc?view=revision&revision=1096691
https://issues.apache.org/jira/browse/DERBY-4443 yes bpendleton
http://svn.apache.org/viewvc?view=revision&revision=1098033
https://issues.apache.org/jira/browse/DERBY-5211 yes bpendleton
http://svn.apache.org/viewvc?view=revision&revision=1098040
https://issues.apache.org/jira/browse/DERBY-5163 yes lilywei
http://svn.apache.org/viewvc?view=revision&revision=1101059
https://issues.apache.org/jira/browse/DERBY-5222 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1102730
https://issues.apache.org/jira/browse/DERBY-5210 no  kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1103742
https://issues.apache.org/jira/browse/DERBY-5222 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1103992
https://issues.apache.org/jira/browse/DERBY-1482 no  mamta
http://svn.apache.org/viewvc?view=revision&revision=1104365
https://issues.apache.org/jira/browse/DERBY-5236 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1124438
https://issues.apache.org/jira/browse/DERBY-5200 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1125299
https://issues.apache.org/jira/browse/DERBY-5068 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1125353
https://issues.apache.org/jira/browse/DERBY-5068 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1125447
https://issues.apache.org/jira/browse/DERBY-5238 yes chaase3
http://svn.apache.org/viewvc?view=revision&revision=1125453
https://issues.apache.org/jira/browse/DERBY-1482/5121 yes mamta
http://svn.apache.org/viewvc?view=revision&revision=1126468
https://issues.apache.org/jira/browse/DERBY-5239 yes? kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1127886
https://issues.apache.org/jira/browse/DERBY-5246 yes? kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1128243
https://issues.apache.org/jira/browse/DERBY-4670 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1128942
https://issues.apache.org/jira/browse/DERBY-5251 yes bpenleton
http://svn.apache.org/viewvc?view=revision&revision=1129117
https://issues.apache.org/jira/browse/DERBY-5080 no? kristwaa
http://svn.apache.org/viewvc?view=revision&revision=1129132
https://issues.apache.org/jira/browse/DERBY-5080 no? kristwaa
http://svn.apache.org/viewvc?view=revision&revision=1130743
https://issues.apache.org/jira/browse/DERBY-4795 yes tiago
http://svn.apache.org/viewvc?view=revision&revision=1130964
https://issues.apache.org/jira/browse/DERBY-5256 no? kristwaa
http://svn.apache.org/viewvc?view=revision&revision=1131030
https://issues.apache.org/jira/browse/DERBY-5097 yes rhillegas
http://svn.apache.org/viewvc?view=revision&revision=1132648
https://issues.apache.org/jira/browse/DERBY-5145 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1132747
https://issues.apache.org/jira/browse/DERBY-5014 yes tiago
http://svn.apache.org/viewvc?view=revision&revision=1133123
https://issues.apache.org/jira/browse/DERBY-5260 yes dag
http://svn.apache.org/viewvc?view=revision&revision=1133273
?https://issues.apache.org/jira/browse/DERBY-5260? yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1133304
https://issues.apache.org/jira/browse/DERBY-5108 yes kristwaa
http://svn.apache.org/viewvc?view=revision&revision=1133317
https://issues.apache.org/jira/browse/DERBY-5108 yes kristwaa
http://svn.apache.org/viewvc?view=revision&revision=1134139
https://issues.apache.org/jira/browse/DERBY-5252 yes bpendleton
http://svn.apache.org/viewvc?view=revision&revision=1134467
https://issues.apache.org/jira/browse/DERBY-1482 yes mamta
http://svn.apache.org/viewvc?view=revision&revision=1135226
https://issues.apache.org/jira/browse/DERBY-4437 no? rhillegas
http://svn.apache.org/viewvc?view=revision&revision=1135383
https://issues.apache.org/jira/browse/DERBY-3913 yes mamta
http://svn.apache.org/viewvc?view=revision&revision=1135404
https://issues.apache.org/jira/browse/DERBY-3913 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1135432
https://issues.apache.org/jira/browse/DERBY-5267 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1135545
https://issues.apache.org/jira/browse/DERBY-5275 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1135754
https://issues.apache.org/jira/browse/DERBY-4437 yes rhillegas
http://svn.apache.org/viewvc?view=revision&revision=1135976
https://issues.apache.org/jira/browse/DERBY-5269 yes kristwaa
http://svn.apache.org/viewvc?view=revision&revision=1136011
https://issues.apache.org/jira/browse/DERBY-4089 no? kristwaa
http://svn.apache.org/viewvc?view=revision&revision=1136036
https://issues.apache.org/jira/browse/DERBY-4437 no? rhillegas
http://svn.apache.org/viewvc?view=revision&revision=1136363
https://issues.apache.org/jira/browse/DERBY-4137 yes kristwaa
http://svn.apache.org/viewvc?view=revision&revision=1136371
https://issues.apache.org/jira/browse/DERBY-5274 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1136397
https://issues.apache.org/jira/browse/DERBY-5239 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1136844
https://issues.apache.org/jira/browse/DERBY-5278 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1137213
https://issues.apache.org/jira/browse/DERBY-5217 yes kahatlen
http://svn.apache.org/viewvc?view=revision&revision=1137258
https://issues.apache.org/jira/browse/DERBY-5156 yes bpendleton

Re: backports for 10.8.2...

Posted by Kathey Marsden <km...@sbcglobal.net>.
On 6/21/2011 5:09 AM, Knut Anders Hatlen wrote:
>
> The list of issues you wanted feedback on contained many improvements,
> not only bug fixes. Should we mark issues that implement new features
> with derby_backport_reject_10_8, or would it be sufficient to use the
> label on bug fixes that shouldn't be backported? (I think previous
> backporting efforts have focused on issues reported as bugs.)
>
I think  if using Jira queries, features don't need the label but can 
just be excluded from the query, e.g.
project = DERBY AND Type not in ("New Feature",Improvement) AND labels 
not in (derby_backport_reject_10_8)  and resolution = fixed  AND 
fixVersion not in ("10.8.1.2","10.8.1.4")
  and fixVersion in ("10.9.0.0")

I


Re: backports for 10.8.2...

Posted by Knut Anders Hatlen <kn...@oracle.com>.
Myrna van Lunteren <m....@gmail.com> writes:

> On Mon, Jun 20, 2011 at 2:20 PM, Kathey Marsden
> <km...@sbcglobal.net> wrote:
>> On 6/20/2011 12:29 PM, Mike Matrigali wrote:
>>>
>>> If you determine an issue is not appropriate for backport could you
>>> mark the JIRA issue.  Kathey came up with standard for this during
>>> the last backport effort.
>>>
>> The issues rejected for backport can be marked with the labels
>> derby_backport_reject_<version> e.g. derby_backport_reject_10_8
>>
>> where <version> is the highest version where backport was rejected.
>> So, if we decided a fix  does not make sense to backport to 10.8,
>> It would be labelled derby_backport_reject_10_8.
>>
>>
>> Then the labels  can be used in Jira queries, for example:
>> project = DERBY AND labels not in (derby_backport_reject_10_8)  and
>> resolution = fixed  AND fixVersion not in ("10.8.1.2","10.8.1.4","10.8.2.0")
>> and fixVersion in ("10.9.0.0")
>> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+DERBY+AND+labels+not+in+%28derby_backport_reject_10_8%29++and+resolution+%3D+fixed++AND+fixVersion+not+in+%28%2210.8.1.2%22%2C%2210.8.1.4%22%2C%2210.8.2.0%22%29+and+fixVersion+in+%28%2210.9.0.0%22%29&tempMax=1000
>>
>>
>>
>
> Thanks for the info, derby_backport_reject_10_8 sounds like the thing
> to use. Sometimes though even if the fix for the issue is not suitable
> for backport, it may still be feasible to backport a new test.

The list of issues you wanted feedback on contained many improvements,
not only bug fixes. Should we mark issues that implement new features
with derby_backport_reject_10_8, or would it be sufficient to use the
label on bug fixes that shouldn't be backported? (I think previous
backporting efforts have focused on issues reported as bugs.)

-- 
Knut Anders

Re: backports for 10.8.2...

Posted by Myrna van Lunteren <m....@gmail.com>.
On Mon, Jun 20, 2011 at 2:20 PM, Kathey Marsden
<km...@sbcglobal.net> wrote:
> On 6/20/2011 12:29 PM, Mike Matrigali wrote:
>>
>> If you determine an issue is not appropriate for backport could you
>> mark the JIRA issue.  Kathey came up with standard for this during
>> the last backport effort.
>>
> The issues rejected for backport can be marked with the labels
> derby_backport_reject_<version> e.g. derby_backport_reject_10_8
>
> where <version> is the highest version where backport was rejected.
> So, if we decided a fix  does not make sense to backport to 10.8,
> It would be labelled derby_backport_reject_10_8.
>
>
> Then the labels  can be used in Jira queries, for example:
> project = DERBY AND labels not in (derby_backport_reject_10_8)  and
> resolution = fixed  AND fixVersion not in ("10.8.1.2","10.8.1.4","10.8.2.0")
> and fixVersion in ("10.9.0.0")
> https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+DERBY+AND+labels+not+in+%28derby_backport_reject_10_8%29++and+resolution+%3D+fixed++AND+fixVersion+not+in+%28%2210.8.1.2%22%2C%2210.8.1.4%22%2C%2210.8.2.0%22%29+and+fixVersion+in+%28%2210.9.0.0%22%29&tempMax=1000
>
>
>

Thanks for the info, derby_backport_reject_10_8 sounds like the thing
to use. Sometimes though even if the fix for the issue is not suitable
for backport, it may still be feasible to backport a new test.

Myrna

Re: backports for 10.8.2...

Posted by Kathey Marsden <km...@sbcglobal.net>.
On 6/20/2011 12:29 PM, Mike Matrigali wrote:
> If you determine an issue is not appropriate for backport could you
> mark the JIRA issue.  Kathey came up with standard for this during
> the last backport effort.
>
The issues rejected for backport can be marked with the labels
derby_backport_reject_<version> e.g. derby_backport_reject_10_8

where <version> is the highest version where backport was rejected.
So, if we decided a fix  does not make sense to backport to 10.8,
It would be labelled derby_backport_reject_10_8.


Then the labels  can be used in Jira queries, for example:
project = DERBY AND labels not in (derby_backport_reject_10_8)  and 
resolution = fixed  AND fixVersion not in 
("10.8.1.2","10.8.1.4","10.8.2.0") and fixVersion in ("10.9.0.0")
https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project+%3D+DERBY+AND+labels+not+in+%28derby_backport_reject_10_8%29++and+resolution+%3D+fixed++AND+fixVersion+not+in+%28%2210.8.1.2%22%2C%2210.8.1.4%22%2C%2210.8.2.0%22%29+and+fixVersion+in+%28%2210.9.0.0%22%29&tempMax=1000



Re: backports for 10.8.2...

Posted by Mike Matrigali <mi...@sbcglobal.net>.
If you determine an issue is not appropriate for backport could you
mark the JIRA issue.  Kathey came up with standard for this during
the last backport effort.

Also if you think the issue is appropriate for backport but don't
have time or inclination, post that info also.

/mikem

Myrna van Lunteren wrote:
> Hi,
> 
> I (wearing the release manager hat) have tentatively scheduled a bug
> fix release off the 10.8 branch for mid-September.
> 
> I've been looking a little at the commits, and it seems to me that a
> fair number of bug fixes have gone in to trunk already that haven't
> been backported to 10.8.
> 
> Here's a list of revisions (with bug numbers) that I think haven't
> been backported, and the committer.
> Please look over this list, and if you can, backport any issues that
> are not new features and would cause no incompatibility from trunk to
> 10.8.
> 
> If you think the revisions are ok to be backported, but you have no
> time to do the backport yourself, please let me know, and I'll work on
> it in the next couple of weeks.
> If I listed revisions that are ok to be backported, but they aren't,
> or I've listed them as not to be backported, but they are, also let me
> know.
> I would especially like input on those with ? (question marks).
> 
> I'll send out another email in August, and discuss items committed during July.
> 
> Myrna
> 
> revision      bug#     backport ok     committer
> -----------------------------------------------------------------------
> http://svn.apache.org/viewvc?view=revision&revision=1096361 no-JIRA yes mamta
> http://svn.apache.org/viewvc?view=revision&revision=1096691
> https://issues.apache.org/jira/browse/DERBY-4443 yes bpendleton
> http://svn.apache.org/viewvc?view=revision&revision=1098033
> https://issues.apache.org/jira/browse/DERBY-5211 yes bpendleton
> http://svn.apache.org/viewvc?view=revision&revision=1098040
> https://issues.apache.org/jira/browse/DERBY-5163 yes lilywei
> http://svn.apache.org/viewvc?view=revision&revision=1101059
> https://issues.apache.org/jira/browse/DERBY-5222 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1102730
> https://issues.apache.org/jira/browse/DERBY-5210 no  kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1103742
> https://issues.apache.org/jira/browse/DERBY-5222 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1103992
> https://issues.apache.org/jira/browse/DERBY-1482 no  mamta
> http://svn.apache.org/viewvc?view=revision&revision=1104365
> https://issues.apache.org/jira/browse/DERBY-5236 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1124438
> https://issues.apache.org/jira/browse/DERBY-5200 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1125299
> https://issues.apache.org/jira/browse/DERBY-5068 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1125353
> https://issues.apache.org/jira/browse/DERBY-5068 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1125447
> https://issues.apache.org/jira/browse/DERBY-5238 yes chaase3
> http://svn.apache.org/viewvc?view=revision&revision=1125453
> https://issues.apache.org/jira/browse/DERBY-1482/5121 yes mamta
> http://svn.apache.org/viewvc?view=revision&revision=1126468
> https://issues.apache.org/jira/browse/DERBY-5239 yes? kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1127886
> https://issues.apache.org/jira/browse/DERBY-5246 yes? kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1128243
> https://issues.apache.org/jira/browse/DERBY-4670 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1128942
> https://issues.apache.org/jira/browse/DERBY-5251 yes bpenleton
> http://svn.apache.org/viewvc?view=revision&revision=1129117
> https://issues.apache.org/jira/browse/DERBY-5080 no? kristwaa
> http://svn.apache.org/viewvc?view=revision&revision=1129132
> https://issues.apache.org/jira/browse/DERBY-5080 no? kristwaa
> http://svn.apache.org/viewvc?view=revision&revision=1130743
> https://issues.apache.org/jira/browse/DERBY-4795 yes tiago
> http://svn.apache.org/viewvc?view=revision&revision=1130964
> https://issues.apache.org/jira/browse/DERBY-5256 no? kristwaa
> http://svn.apache.org/viewvc?view=revision&revision=1131030
> https://issues.apache.org/jira/browse/DERBY-5097 yes rhillegas
> http://svn.apache.org/viewvc?view=revision&revision=1132648
> https://issues.apache.org/jira/browse/DERBY-5145 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1132747
> https://issues.apache.org/jira/browse/DERBY-5014 yes tiago
> http://svn.apache.org/viewvc?view=revision&revision=1133123
> https://issues.apache.org/jira/browse/DERBY-5260 yes dag
> http://svn.apache.org/viewvc?view=revision&revision=1133273
> ?https://issues.apache.org/jira/browse/DERBY-5260? yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1133304
> https://issues.apache.org/jira/browse/DERBY-5108 yes kristwaa
> http://svn.apache.org/viewvc?view=revision&revision=1133317
> https://issues.apache.org/jira/browse/DERBY-5108 yes kristwaa
> http://svn.apache.org/viewvc?view=revision&revision=1134139
> https://issues.apache.org/jira/browse/DERBY-5252 yes bpendleton
> http://svn.apache.org/viewvc?view=revision&revision=1134467
> https://issues.apache.org/jira/browse/DERBY-1482 yes mamta
> http://svn.apache.org/viewvc?view=revision&revision=1135226
> https://issues.apache.org/jira/browse/DERBY-4437 no? rhillegas
> http://svn.apache.org/viewvc?view=revision&revision=1135383
> https://issues.apache.org/jira/browse/DERBY-3913 yes mamta
> http://svn.apache.org/viewvc?view=revision&revision=1135404
> https://issues.apache.org/jira/browse/DERBY-3913 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1135432
> https://issues.apache.org/jira/browse/DERBY-5267 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1135545
> https://issues.apache.org/jira/browse/DERBY-5275 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1135754
> https://issues.apache.org/jira/browse/DERBY-4437 yes rhillegas
> http://svn.apache.org/viewvc?view=revision&revision=1135976
> https://issues.apache.org/jira/browse/DERBY-5269 yes kristwaa
> http://svn.apache.org/viewvc?view=revision&revision=1136011
> https://issues.apache.org/jira/browse/DERBY-4089 no? kristwaa
> http://svn.apache.org/viewvc?view=revision&revision=1136036
> https://issues.apache.org/jira/browse/DERBY-4437 no? rhillegas
> http://svn.apache.org/viewvc?view=revision&revision=1136363
> https://issues.apache.org/jira/browse/DERBY-4137 yes kristwaa
> http://svn.apache.org/viewvc?view=revision&revision=1136371
> https://issues.apache.org/jira/browse/DERBY-5274 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1136397
> https://issues.apache.org/jira/browse/DERBY-5239 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1136844
> https://issues.apache.org/jira/browse/DERBY-5278 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1137213
> https://issues.apache.org/jira/browse/DERBY-5217 yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1137258
> https://issues.apache.org/jira/browse/DERBY-5156 yes bpendleton
> 


Re: backports for 10.8.2...

Posted by Kristian Waagan <kr...@oracle.com>.
On 20.06.11 21:19, Rick Hillegas wrote:
> On 6/20/11 11:48 AM, Myrna van Lunteren wrote:
>> Hi,

< snip>

>> Myrna
>>
>> revision bug# backport ok committer
>> -----------------------------------------------------------------------
>>
>> http://svn.apache.org/viewvc?view=revision&revision=1131030
>> https://issues.apache.org/jira/browse/DERBY-5097 yes rhillegas
> I think that Kristian did the work on this issue so he's the expert.

It has been backported.

-- 
Kristian

>> https://issues.apache.org/jira/browse/DERBY-4437 no? rhillegas
> There are a number of commits on this issue already and I expect there
> will be more. So far I have avoided backporting any of this work to the
> 10.8 branch because one person felt that the behavior change was bigger
> than we commonly tolerate in a maintenance release. The latest patch on
> that issue may address those concerns. Once I commit that work, I will
> ask again whether there are any objections to porting this work to 10.8.2.
>
> Thanks,
> -Rick


Re: backports for 10.8.2...

Posted by Rick Hillegas <ri...@oracle.com>.
On 6/20/11 11:48 AM, Myrna van Lunteren wrote:
> Hi,
>
> I (wearing the release manager hat) have tentatively scheduled a bug
> fix release off the 10.8 branch for mid-September.
>
> I've been looking a little at the commits, and it seems to me that a
> fair number of bug fixes have gone in to trunk already that haven't
> been backported to 10.8.
>
> Here's a list of revisions (with bug numbers) that I think haven't
> been backported, and the committer.
> Please look over this list, and if you can, backport any issues that
> are not new features and would cause no incompatibility from trunk to
> 10.8.
>
> If you think the revisions are ok to be backported, but you have no
> time to do the backport yourself, please let me know, and I'll work on
> it in the next couple of weeks.
> If I listed revisions that are ok to be backported, but they aren't,
> or I've listed them as not to be backported, but they are, also let me
> know.
> I would especially like input on those with ? (question marks).
>
> I'll send out another email in August, and discuss items committed during July.
>
> Myrna
>
> revision      bug#     backport ok     committer
> -----------------------------------------------------------------------
>
> http://svn.apache.org/viewvc?view=revision&revision=1131030
> https://issues.apache.org/jira/browse/DERBY-5097 yes rhillegas
I think that Kristian did the work on this issue so he's the expert.
> https://issues.apache.org/jira/browse/DERBY-4437 no? rhillegas
There are a number of commits on this issue already and I expect there 
will be more. So far I have avoided backporting any of this work to the 
10.8 branch because one person felt that the behavior change was bigger 
than we commonly tolerate in a maintenance release. The latest patch on 
that issue may address those concerns. Once I commit that work, I will 
ask again whether there are any objections to porting this work to 10.8.2.

Thanks,
-Rick

Re: backports for 10.8.2...

Posted by Knut Anders Hatlen <kn...@oracle.com>.
Myrna van Lunteren <m....@gmail.com> writes:

> Hi,
>
> I (wearing the release manager hat) have tentatively scheduled a bug
> fix release off the 10.8 branch for mid-September.
>
> I've been looking a little at the commits, and it seems to me that a
> fair number of bug fixes have gone in to trunk already that haven't
> been backported to 10.8.
>
> Here's a list of revisions (with bug numbers) that I think haven't
> been backported, and the committer.
>
> Please look over this list, and if you can, backport any issues that
> are not new features and would cause no incompatibility from trunk to
> 10.8.
>
> If you think the revisions are ok to be backported, but you have no
> time to do the backport yourself, please let me know, and I'll work on
> it in the next couple of weeks.
> If I listed revisions that are ok to be backported, but they aren't,
> or I've listed them as not to be backported, but they are, also let me
> know.
> I would especially like input on those with ? (question marks).
>
> I'll send out another email in August, and discuss items committed during July.
>
> Myrna
>
> revision      bug#     backport ok     committer
> -----------------------------------------------------------------------

I'll backport the fixes for these issues:

> https://issues.apache.org/jira/browse/DERBY-5222 yes kahatlen
> https://issues.apache.org/jira/browse/DERBY-5239 yes? kahatlen
> https://issues.apache.org/jira/browse/DERBY-5274 yes kahatlen
> https://issues.apache.org/jira/browse/DERBY-5278 yes kahatlen

These ones would be best not to backport (marked with
derby_backport_reject_10_8):

> https://issues.apache.org/jira/browse/DERBY-5210 no  kahatlen
> https://issues.apache.org/jira/browse/DERBY-5068 yes kahatlen

These are just minor improvements that should be harmless to backport,
but I don't see that backporting them is worth the effort, so I won't do
it myself:

> https://issues.apache.org/jira/browse/DERBY-5200 yes kahatlen
> https://issues.apache.org/jira/browse/DERBY-5246 yes? kahatlen
> https://issues.apache.org/jira/browse/DERBY-4670 yes kahatlen
> https://issues.apache.org/jira/browse/DERBY-5145 yes kahatlen
> https://issues.apache.org/jira/browse/DERBY-5267 yes kahatlen
> https://issues.apache.org/jira/browse/DERBY-5275 yes kahatlen
> https://issues.apache.org/jira/browse/DERBY-5217 yes kahatlen

The commit below just adds a disabled test case to show the bug (the bug
is not fixed, and the issue is still open). Not worthwhile backporting.
If the issue is fixed, we can backport all commits then.

> http://svn.apache.org/viewvc?view=revision&revision=1104365
> https://issues.apache.org/jira/browse/DERBY-5236 yes kahatlen

The next two commits are followups to issues others have been working
on. If the main patches for the issues are backported, these should be
backported too. But the changes in these issues are so small that I
wouldn't bother backporting them (DERBY-5260 just removes an unused
parameter, and the net effect of the patches for DERBY-3913 is a slight
reordering of the words in a message).

> http://svn.apache.org/viewvc?view=revision&revision=1133273
> ?https://issues.apache.org/jira/browse/DERBY-5260? yes kahatlen
> http://svn.apache.org/viewvc?view=revision&revision=1135404
> https://issues.apache.org/jira/browse/DERBY-3913 yes kahatlen

-- 
Knut Anders