I will start looking at 10.10 backport issues since 10.11 backport query does not return any issues.
On Wed, Sep 24, 2014 at 4:28 PM, Myrna van Lunteren <m.v.lunte...@gmail.com> wrote: > I said earlier that the 10.10 backport query returned 108 rows. I modified > it further and now there's only 37 rows (some more moved off the list > because Mike's work). > > Myrna > > On Wed, Sep 24, 2014 at 4:09 PM, mike matrigali <mikema...@gmail.com> > wrote: > >> I am working through the 10.11 backport query. It needed some more work >> as it missed 10.10 bugs fixed in different releases. Also am >> doing a quick triage to see which bugs are not appropriate for 10.10 >> backport and adding labels. If anyone disagrees with my initial >> assessment please add comments on why and just remove the label. >> >> /mikem >> >> >> On 9/24/2014 3:13 PM, Myrna van Lunteren wrote: >> >>> Hi, >>> >>> I'm interested in backporting suitable fixes from trunk to the 10.11 and >>> 10.10 branches. >>> >>> I've modified my existing query for backporting to 10.10 >>> 'derby_10_10_backport_query': >>> https://issues.apache.org/jira/issues/?filter=12326503 >>> This currently results in 108 rows. >>> >>> I've also created a similar query for backporting to 10.11: >>> 'derby_10_11_backport_query': >>> https://issues.apache.org/jira/issues/?filter=12329357 >>> This currently results in 11 rows. >>> >>> If you spot something wrong with these queries let me know. >>> >>> If you can join me in backporting please pick issues from the list, >>> reopen, assign yourself, do the back port and afterward reassign the >>> original owner and close. >>> If it is found an issue cannot or should not get backported, please tack >>> on the appropriate 'derby_backport_reject_10.10' or >>> 'derby_backport_reject_10_11' label. >>> >>> Thanks, >>> Myrna >>> >>> >>> >> >
