db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1029) Backout boolean work from the 10.2 branch immediately after the branch is created
Date Thu, 20 Jul 2006 16:25:14 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1029?page=comments#action_12422447 ] 
            
Rick Hillegas commented on DERBY-1029:
--------------------------------------

Committed derby-1029_v05.diff at subversion revision 423976. The following tests were run:

1) The script in DERBY-887 now runs identically to the way it did against 10.1.

2) The compatibility suite runs cleanly.

3) Derbyall runs cleanly against jar files under 1.3 except for OutBufferedStream. That test
hangs with or without this patch.

4) Derbyall runs cleanly against jar files under 1.4 and 1.5.

5 Derbyall runs cleanly against jar files under 1.6 except for known problems in jdbc40 suite
(which appeared with Mustang build 91) and the diff in procedureInTrigger (see DERBY-550).


> Backout boolean work from the 10.2 branch immediately after the branch is created
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-1029
>                 URL: http://issues.apache.org/jira/browse/DERBY-1029
>             Project: Derby
>          Issue Type: Sub-task
>          Components: SQL
>    Affects Versions: 10.2.0.0
>            Reporter: Kathey Marsden
>         Assigned To: Rick Hillegas
>            Priority: Blocker
>             Fix For: 10.2.0.0
>
>         Attachments: derby-1029_v03.diff, derby-1029_v05.diff
>
>
> There was discussion on the list regarding how  to handle this issue but keep the BOOLEAN
work for inclusion in future releases.  The approach discussed was to back the DERBY-499 work
out of the 10.2 branch as soon as it is created, but leave it in the trunk
> I think this an acceptable solution but  only if we can get someone assigned to this
issue that is willing to commit now to doing that work as soon as we branch.   The reverse
merge may be messy at that point do to other changes that have gone in.  
>  
> Is there someone who will volunteer to do this work and assign themselves to this issue?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message