db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (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, 11 May 2006 00:10:05 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1029?page=comments#action_12378998 ] 

Daniel John Debrunner commented on DERBY-1029:

With the 10.2 release being delayed what's the current plan for this, fix BOOLEAN to match
the spec or continue with removing it from the branch? Seems like with the more time available,
Rick, you could continue your original itch to implement BOOLEAN?

> 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
>         Type: Sub-task

>   Components: SQL
>     Versions:
>     Reporter: Kathey Marsden
>     Assignee: Rick Hillegas
>     Priority: Blocker
>      Fix For:

> 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:
For more information on JIRA, see:

View raw message