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 2009/04/17 22:56:14 UTC
[jira] Created: (DERBY-4170) Create 10.4_10.5testCompat branch to
facilitate compatibility and upgrade testing for 10.5
Create 10.4_10.5testCompat branch to facilitate compatibility and upgrade testing for 10.5
------------------------------------------------------------------------------------------
Key: DERBY-4170
URL: https://issues.apache.org/jira/browse/DERBY-4170
Project: Derby
Issue Type: Task
Components: Test
Affects Versions: 10.4.2.1
Reporter: Kathey Marsden
Assignee: Kathey Marsden
Priority: Minor
It would be useful to have a a branch based off of 10.4 that has the expected test and canon changes for 10.4 tests run against 10.5 which reflect intentional behavior changes. This is useful for soft upgrade and client/server compatibility testing, so that the same failures don't have to be analyzed repeatedly. It also makes for good documentation of intended behavior changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-4170) Create 10.4_10.5testCompat branch to
facilitate compatibility and upgrade testing for 10.5
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12700376#action_12700376 ]
Kathey Marsden commented on DERBY-4170:
---------------------------------------
Created the branch. The command so I have it for reference next time was:
svn copy -r 689064 https://svn.apache.org/repos/asf/db/derby/code/branches/10.4/ https://svn.apache.org/repos/asf/db/derby/code/branches/10.4_10.5testCompat/ -m "Creating compat test branch for running 10.4 tests against 10.5. based off of 10.4.2.0"
Now we just need to identify what test changes need to be backported to get the tests on the branch to run cleanly against 10.5.
> Create 10.4_10.5testCompat branch to facilitate compatibility and upgrade testing for 10.5
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-4170
> URL: https://issues.apache.org/jira/browse/DERBY-4170
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.2.1
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
>
> It would be useful to have a a branch based off of 10.4 that has the expected test and canon changes for 10.4 tests run against 10.5 which reflect intentional behavior changes. This is useful for soft upgrade and client/server compatibility testing, so that the same failures don't have to be analyzed repeatedly. It also makes for good documentation of intended behavior changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (DERBY-4170) Create 10.4_10.5testCompat branch to
facilitate compatibility and upgrade testing for 10.5
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-4170.
-----------------------------------
Resolution: Won't Fix
Suran analyzed the results manually for 10.5/10.4 upgrade testing, so I won't do this.
> Create 10.4_10.5testCompat branch to facilitate compatibility and upgrade testing for 10.5
> ------------------------------------------------------------------------------------------
>
> Key: DERBY-4170
> URL: https://issues.apache.org/jira/browse/DERBY-4170
> Project: Derby
> Issue Type: Task
> Components: Test
> Affects Versions: 10.4.2.1
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
>
> It would be useful to have a a branch based off of 10.4 that has the expected test and canon changes for 10.4 tests run against 10.5 which reflect intentional behavior changes. This is useful for soft upgrade and client/server compatibility testing, so that the same failures don't have to be analyzed repeatedly. It also makes for good documentation of intended behavior changes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.