Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@trafficserver.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.0 \(3094\))
Subject: Re: [VOTE] Release Apache Traffic Server 6.0.0 (RC3)
From: Leif Hedstrom <zwoop@apache.org>
In-Reply-To: <800373317.47517.1442330080799.JavaMail.zimbra@brainsware.org>
Date: Tue, 15 Sep 2015 14:46:20 -0700
Cc: users <users@trafficserver.apache.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <0EDBC941-7832-4251-BC5B-13A045C95041@apache.org>
References: <C471995D-C7A6-447B-8F96-6DF77FB26CC1@apache.org>
 <800373317.47517.1442330080799.JavaMail.zimbra@brainsware.org>
To: dev@trafficserver.apache.org


> On Sep 15, 2015, at 8:14 AM, Igor Gali=C4=87 <i.galic@brainsware.org> =
wrote:
>=20
>=20
>=20
> Bryan,
>=20
> ----- On 15 Sep, 2015, at 00:53, Bryan Call bcall@apache.org wrote:
>=20
>> I've prepared a release for 6.0.0 (RC3) which is the next major =
version of
>> Apache Traffic Server.  This version breaks binary compatibility and =
plugins
>> will need to be recompiled.  This is detailed in our Release =
Management
>> document:
>=20
> it's not clear from any of the links below how / why / where we're =
breaking
> binary compatibility.


The gist is that you really should recompile any plugins you have =
against the new APIs on every major release. :) But yes, the =
documentation definitely needs to be upgraded, including a few =
deprecated APIs.

=E2=80=94 Leif