[redland-dev] Raptor V2 rollout plan change

[Dave Beckett]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I've been getting some feedback on the plan I announced on 7th November.

First, the Raptor V1 end of life is still happening.  Only security bug
fixes if they turn up, no other bug fixes, no new features.

On Raptor V2, I think it's turning out to be too tricky to have code in
Rasqal and librdf that have to know if they linked with raptor V1 or V2
at configure, build and runtime.  I've made mistakes here and managed
to link code with raptor v1 and v2 at the same time, getting mysterious
crashes and I've got other people reporting this too.

Having thought about it, I think the easier plan is instead of a long
rollout of supporting building Rasqal and librdf alternatively against
raptor V1 and V2, is to make a clean break, with more short term pain but
less chance of crashes related to wrong version.

So the proposed plan in time order is something like this:

1. "Soon" another Raptor V2 beta release with some fixes, minor API changes.

2. (December?) Raptor V2 2.0.0 final release

3. Rasqal next release requires Raptor V2 and bumps the librasqal soname
major version

4. librdf next release requires Rasqal above and bumps librdf soname major
version.

5. bindings next release requires librdf above


Comments?

Dave
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)

iD8DBQFM6W2wQ+ySUE9xlVoRApqMAKCCk913DDbajpBfGif99SL28+aQAQCgo6T4
Nb8g2AQ6Gm4VSFAatvfIPT0=
=+lYh
-----END PGP SIGNATURE-----