Mailing-List: contact issues-help@stdcxx.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@stdcxx.apache.org
Message-ID: <114524476.1216337131709.JavaMail.jira@brutus>
Date: Thu, 17 Jul 2008 16:25:31 -0700 (PDT)
From: "Martin Sebor (JIRA)" <jira@apache.org>
To: issues@stdcxx.apache.org
Subject: [jira] Updated: (STDCXX-731) framework to verify binary
 compatibility
In-Reply-To: <1942912077.1203457243459.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/STDCXX-731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Sebor updated STDCXX-731:
--------------------------------

    Fix Version/s:     (was: 4.2.2)
                   4.3.0

It sure would be nice to have but who's got the time to write it...? Deferred until 4.3.0.

> framework to verify binary compatibility
> ----------------------------------------
>
>                 Key: STDCXX-731
>                 URL: https://issues.apache.org/jira/browse/STDCXX-731
>             Project: C++ Standard Library
>          Issue Type: Improvement
>          Components: Test Harness
>    Affects Versions: 4.2.0
>            Reporter: Martin Sebor
>             Fix For: 4.3.0
>
>   Original Estimate: 80h
>  Remaining Estimate: 80h
>
> In the 4.2.0 release we ran into binary incompatibilities late in the release cycle that ended up costly to fix. What would have prevented the incompatibilities, or at least allowed us to detect them early on, would have been an automated framework to verify the binary compatibility of the library. This is a placeholder issue to design and implement such a framework.
> I'm guesstimating the effort of putting something like this in place at 80 hours, possibly more.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.