Message-ID: <4DE7C3D4.7010601@fifthhorseman.net>
Date: Thu, 02 Jun 2011 13:09:40 -0400
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.9.2.17) Gecko/20110516 Icedove/3.1.10
MIME-Version: 1.0
To: notmuch <notmuch@notmuchmail.org>
Subject: Re: Fwd: Re: compile error of current git on F15
References: <4DE52798.9020906@fifthhorseman.net> <4DE787E7.7060400@gnome.org>
In-Reply-To: <4DE787E7.7060400@gnome.org>
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature";
	boundary="------------enigC5B868187D4592CDEE838171"
Cc: Jeffrey Stedfast <fejj@gnome.org>
Precedence: list
Reply-To: notmuch <notmuch@notmuchmail.org>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigC5B868187D4592CDEE838171
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I got the following response off-list from the gmime lead, which he's ok
with my re-posting here:

On 06/02/2011 08:53 AM, Jeffrey Stedfast wrote:
> I don't know why Fedora 15 ships 2.5.x, that seems like a really silly
> thing to do. I think I recall the Balsa guys bringing this up in the
> past and I thought I explained to the Fedora guys that 2.5.x was API
> unstable. Perhaps there was some misunderstanding or something.
>=20
> That said, as far as timeline goes, I think 2.6 is basically ready for =
a
> final release, I've just been busy with other stuff lately. Assuming yo=
u
> don't have any major outstanding issues with the crypto stuff, I can
> just roll out a 2.6.0 release (which hopefully F15 will pick up, or, if=

> not, just check gmime-2.6 >=3D 2.5.7) at any time.
>=20
> I think notmuch is the only thing making heavy use of the 2.6 crypto
> stuff right now, so you guys have priority.

So this actually makes me re-think my earlier objections to patches
against an unstable API, on two grounds:

 0) if we're the driving force for 2.6 crypto, we should exercise it so
we can give reasonable feedback before stabilization happens.

 1) it sounds like the API is near stabilization anyway, so it won't be
too much hair-pulling, other than any changes we recommend.

So if we can just get 0.6 released, i'll commit to making patches to
support gmime 2.6 for the next version.

(i'll probably start by urging debian's gmime folks to put a version of
gmime2.6 into the experimental repo for us to play with)

	--dkg

PS i still recommend that F15 should not ship gmime2.6 by default.  that
seems like a recipe for this kind of trouble.


--------------enigC5B868187D4592CDEE838171
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQJ8BAEBCgBmBQJN58PVXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQwRUU1QkU5NzkyODJEODBCOUY3NTQwRjFD
Q0QyRUQ5NEQyMTczOUU5AAoJEMzS7ZTSFznpx3EQAJ1gXOer6io+ARDe/opnzaMx
bdFtDRKk57QZ64W92niPW/oN31oeH7m7nEQfjNIcBHQvBiDYQoMvo4a5jjhHXmeV
cQQlP6nAXYvTUQVrqOHgsyRFXAqe/QGOSqNmjyuaBf9KJU7GhI1aqni2ZdbI5goO
KVqOl59NDFGwHk1CtRXfeGBCTCjeNGhZZ5VKKAkheDaf0KBzjr86cJ11WnQqV3d2
j03OOER7zBOsJ3SYOygHHRUEhI66rVPEm/ZBmvNSwibI9aBOOPOD4gav8D2FwSWn
cdsOpJTyJJN0SnNviQW+ovz5uVpVDKPgIEXqSwW1LxvtEpWoanug+E4F+KprFUwH
RO+yKmSmTYt7fL1RP/ox7OGRBdTuLCOwpFxfYkl8R39RVjYmZBWj/UD05XsZtb9G
tV20miT4nAYI1tHEXum3avBfATjrb0lZl44JPitofZRgSKftvDIxgPIGMF4a0HRx
0RnTnlQanbkcGpfKXlFzJDhvg9mJLrw4/t1c89d7aX6UUg3EaQdFExQ7i4TTstSF
Ii8zxMwho+/leRU4UbAx0mQxvQ2seIbY7OeyyRDmVsWP3tGjSHrz8USPjugs4Gns
yZVkw4Avo/3UicYQq0eGKK9OqWLmURfTxF9Jkk0peHbTTDeRMzM+XWEHCrah45Wi
SWnQ23CmlFvbN4+VHnqS
=cut7
-----END PGP SIGNATURE-----

--------------enigC5B868187D4592CDEE838171--