Mailing-List: contact aries-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: aries-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of gcharters@googlemail.com
 designates 209.85.161.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=fYFOuOlRKQUG9yXEw22S9hl+GQcaUmSn5nj1243oGp99AnH2641WqRDQ8UqBkhZjHz
         4O3kNaaoOWWoL8I7vJ1Bp+WbbNzFbMHY+uBk0Lfhxa0rs5QwqKtiLyr7rQsoLwJ19a4C
         T9pRsEvtKBHNjmrIoqHhujEDKOsqhnZ8fKQAM=
MIME-Version: 1.0
In-Reply-To: <BLU128-W1905BF843065363966E83FDFD10@phx.gbl>
References: <BLU128-W1905BF843065363966E83FDFD10@phx.gbl>
Date: Thu, 3 Jun 2010 15:17:58 +0100
Message-ID: <AANLkTilRvSKZ8luTPiUiO-FjE7q0XYvFSxiD0bpvkLD8@mail.gmail.com>
Subject: Re: API/SPI Package versioning policy
From: Graham Charters <gcharters@googlemail.com>
To: aries-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

This is an important discussion to have.  I think we should adopt the
semantic versioning policy outlined in the OSGi Alliance whitepaper:
http://www.osgi.org/wiki/uploads/Links/SemanticVersioning.pdf  .  This
includes guidelines on bundle versioning as well as packages.  I also
prefer trying to keep backward compatibility where practicable.

Regards, Graham.

On 3 June 2010 10:13, Timothy Ward <timothyjward@hotmail.com> wrote:
>
> Hi,
>
> Based on some updates to the JPA container we are considering making some=
 changes to some SPI classes. Obviously this would mean that we needed to c=
hagne the version of the package, but I wanted to raise a discussion on the=
 list about our versioning policy. Are we trying to keep version to version=
 compatability where possible, and if so, how hard? Are we planning to chan=
ge package versions every release (which appears to be what the pom files s=
ay)?
>
> Similarly for bundle versions, if there are no changes to a bundle betwee=
n releases (for example if the JPA blueprint integration didn't change but =
the container added support for weaving) then will the bundle version be ch=
anged anyway? If there are only minor bugfix changes to the bundle will it =
still change major version on release?
>
>
> I know that my preference would be for a strict package versioning policy=
, and trying to keep backward compatability wherever possible. I can't thin=
k of anything more annoying than having to re-write or re-build plugins and=
 extensions for every release. I'm less concerned by bundle versions, but I=
 would lean toward not changing them more often than necessary.
>
> What do people think?
>
> Regards,
>
> Tim
>
> _________________________________________________________________
> http://clk.atdmt.com/UKM/go/195013117/direct/01/
> We want to hear all your funny, exciting and crazy Hotmail stories. Tell =
us now