Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
From: "Bill Stoddard" <bill@wstoddard.com>
To: <dev@httpd.apache.org>
Subject: APACHE_2_0_BRANCH and APR
Date: Mon, 13 Jan 2003 13:35:38 -0500
Message-ID: <JHEPKCEMGPKFFDHHDDKDCEEKGJAA.bill@wstoddard.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Importance: Normal

There are two votes in the STATUS that deserve some on list discussion.

    * APACHE_2_0_BRANCH uses a level of APR code branched from the
      APACHE_2_0_43 tag.
      yes:   trawick, jerenkrantz
      no:    wrowe
        wrowe observes that we have already finished substantial
        bug fixing in 0.9.2-dev since APACHE_2_0_43, so branching
        there seems arbitrary.


    * APACHE_2_0_BRANCH uses a level of APR code versioned 0.9.2-dev
        or later (to 0.9.9), so long it remains binary compatible.
      yes:   wrowe
      no:
        wrowe suggests that when apr chooses to break compatibility,
        httpd would continue to use that last compatible build.

to the best of my knowledge, there is stuff in APR HEAD that breaks binary
compatability. Bill Rowe, how do you plan to reconcile tihs with your vote? In
principle, I agree that branching exactly at APACHE_2_0_43 might not be best
because it does not pick up good fixes, but your alternative does not address
the brokeness that exists now.

Bill