Re: [egit-dev] Consuming jgit/egit for Helios SR1

["Shawn O. Pearce" <spearce@xxxxxxxxxxx>]

Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx> wrote:
> 2010/8/12 Thomas Hallgren <thomas@xxxxxxx>
> >
> > I'm building Buckminster for Helios SR1 and I wonder what update site I
> > should use as input for the egit/jgit bundles. Right now I'm using the
> > helios repository because, not surprisingly, there were some breaking API
> > changes published to your nightly build site.
> >
> > I don't mind these breakages at all, even if you do intend to also publish
> > them in SR1. I can fix my bundles in time for the release and I much prefer
> > that git evolves then being held back by stringent API policies at this
> > point. I just need to know what input to use.
> 
> We shoot for releasing 0.9 with Helios SR1 [1], the 0.9 stream is available
> from the nightly build site.

Right.

Currently we are breaking API between any 0.x and 0.y release, and
the EGit package import specifications reflect that by importing
[0.8.0,0.9.0) or [0.9.0, 0.10.0).  This will continue until our API
and code is stable enough for us to exit incubation and declare a
1.0 release.

Also, right now our 0.x.0 version number is useless.  If you are
using 0.x.0 there may be day-to-day API breakages from our nightly
build site.  We freeze and commit to an API when we release 0.x.1,
and will avoid breaking anything during 0.x.2... if it even occurs.

Ah the hazards of following a still young and incubating project.
:-)

-- 
Shawn.