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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2011/02/01 21:15:28 UTC

[jira] Created: (DERBY-4994) 10.5 backport effort issue (2011)

10.5 backport effort issue (2011)
---------------------------------

                 Key: DERBY-4994
                 URL: https://issues.apache.org/jira/browse/DERBY-4994
             Project: Derby
          Issue Type: Task
            Reporter: Kathey Marsden


This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.

The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.


-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali updated DERBY-4994:
----------------------------------


I suggest we remove DERBY-4582 from the list.  Lily investigated this for the last 10.5 backport effort and decided to not backport.

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992096#comment-12992096 ] 

Mike Matrigali commented on DERBY-4994:
---------------------------------------

I think DERBY-3953 should be taken off the list.  It does not actually have any fix associated with it.  Seems from comments like it is not clear what fixed it.   The comments indicated that
DERBY-3944 has a test for it and that is being backported by me.

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Resolved: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden resolved DERBY-4994.
-----------------------------------

    Resolution: Fixed

Closing this issue out now that the effort is complete and fixes rejected for backport have been labeled.  With the new Jira query interface, you can run queries to see new candidates for backport from within Jira rather than using the Jira VTI e.g. below is the current report for looking at 10.5 fix candidates.


project = DERBY and labels not in (derby_backport_reject_10_5,derby_backport_reject_10_6) and resolution = fixed and affectedVersion in ("10.5.1.1", "10.5.3.0", "10.5.3.2", "10.5.3.1") AND  fixVersion not in ("10.5.1.1", "10.5.3.0", "10.5.3.2", "10.5.3.1") and fixVersion in ("10.8.0.0", "10.7.1.1","10.7.1.3","10.6.1.0", "10.6.2.1", "10.6.2.2", "10.6.2.3")



> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mike Matrigali updated DERBY-4994:
----------------------------------


you should remove DERBY-4743 from the list.  It is just a test change to verify the current behavior.  
Another issue fixed the real bug and was backported.

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996637#comment-12996637 ] 

Kathey Marsden commented on DERBY-4994:
---------------------------------------

I think the porting is done for this issue.  Thank you very much to the community for all the wonderful fixes!  I am going to leave this issue open  as a reminder to myself  to put the derby_backport_reject_<version> tags on the issues that were rejected for backport when I get back in about a  week from now.

Thanks

Kathey

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989901#comment-12989901 ] 

Kathey Marsden commented on DERBY-4994:
---------------------------------------

I reopened the issues to be ported to 10.5 and removed a couple from the list that appeared just cosmetic. When working on porting an issue, temporarily assign yourself and add a comment while doing the work and then reassign to the original owner when you reclose the bug.

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995581#comment-12995581 ] 

Kathey Marsden commented on DERBY-4994:
---------------------------------------

Removed DERBY-4315. See comments in that issue for details.

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Closed] (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden closed DERBY-4994.
---------------------------------


> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>             Fix For: 10.5.3.2
>
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12989588#comment-12989588 ] 

Knut Anders Hatlen commented on DERBY-4994:
-------------------------------------------

> Issues to be fixed will be linked and reopened. As engineers back
> port fixes they can temporarily assign issues to themselves and the
> assign them back to the original own.

If the backporters temporarily assign the issues to themselves, and
they have questions for the original assignee, please make sure to
state who the question is meant for in the JIRA comment. When the
assignee is changed, the original assignee won't get direct JIRA
notifications and may not realize that the question was meant for
him/her. That happened to me a couple of times in the last round of
backporting. I saw the questions fly by on derby-dev, but didn't
realize that they were for me since I saw that someone else was
assigned to the bug and didn't remember that I had worked on it a
while ago.

Also, please make sure to re-assign the issue after the fix has been
backported. Many of the backporters forgot to do that the last time,
and I've found that this has complicated searches in the bug database
(typically when I know who fixed an issue, limit the search to issues
assigned to that person, and cannot find it because the issue no
longer assigned to that person).

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-4994:
----------------------------------

    Fix Version/s: 10.5.3.2

> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>             Fix For: 10.5.3.2
>
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Commented: (DERBY-4994) 10.5 backport effort issue (2011)

Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/DERBY-4994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991553#comment-12991553 ] 

Kathey Marsden commented on DERBY-4994:
---------------------------------------

I took DERBY-4343 off the list as it was a test fix for DERBY-4314 which is not suitable for backport.


> 10.5 backport effort issue (2011)
> ---------------------------------
>
>                 Key: DERBY-4994
>                 URL: https://issues.apache.org/jira/browse/DERBY-4994
>             Project: Derby
>          Issue Type: Task
>            Reporter: Kathey Marsden
>
> This issue will be used to track a back porting effort to the 10.5 branch. Issues to be fixed will be linked and reopened. As engineers back port fixes they can temporarily assign issues to themselves and the assign them back to the original own.
> The linked issues are suggestions, based on a rough analysis.  Please look closely at the issues you pick to back port. If they end up being technically difficult or have behavior changes it may be entirely appropriate to remove them from the list.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira