Mailing-List: contact java-commits-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache Wiki <wikidiffs@apache.org>
To: Apache Wiki <wikidiffs@apache.org>
Date: Wed, 09 Nov 2011 19:32:17 -0000
Message-ID: <20111109193217.82614.33746@eos.apache.org>
Subject: 
 =?utf-8?q?=5BLucene-java_Wiki=5D_Update_of_=22BackwardsCompatibility=22_b?=
 =?utf-8?q?y_Mark_Miller?=
Auto-Submitted: auto-generated

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Lucene-java Wiki" f=
or change notification.

The "BackwardsCompatibility" page has been changed by Mark Miller:
http://wiki.apache.org/lucene-java/BackwardsCompatibility?action=3Ddiff&rev=
1=3D11&rev2=3D12

  =

  A major release may introduce incompatible API and runtime changes.  With=
in minor versions, the transition strategy is to introduce new APIs in rele=
ase '''X.N''', deprecating old APIs, then remove all deprecated APIs in rel=
ease '''X+1.0'''. In some cases, especially with large refactorings across =
major versions, there will be no deprecation path and you will need to read=
 CHANGES and a migration guide to migrate your code.
  =

- Package-private APIs (e.g. methods without any modifier such as public or=
 protected) and those marked as experimental are not supported and thus exe=
mpt from these back-compatibility requirements. They can change without war=
ning or intermediate deprecation.
+ Package-private APIs (e.g. methods without any modifier such as public or=
 protected) and those marked as experimental or internal are not supported =
and thus exempt from these back-compatibility requirements. They can change=
 without warning or intermediate deprecation.
  =

  =3D=3D File Formats =3D=3D
 =20