Re: Re: zope.dottedname doesn't have a CHANGES.txt (again?)

Christian Theune <[email protected]> Tue, 09 Oct 2007 17:23:19 +0200
Newsgroups gmane.comp.web.zope.zope3
Organization gocept gmbh & co. kg
Message-ID <1191943399.8631.29.camel@mindy>
--===============0916314599==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-rip/HU3jFwNu/mwjENNT"


--=-rip/HU3jFwNu/mwjENNT
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Hey,

Am Mittwoch, den 03.10.2007, 13:43 -0400 schrieb Jim Fulton:
> I'm skeptical that such a tool can do that much. Certainly, when we =20
> broke the trunk up, we didn't know what all the issues would be.  We =20
> couldn't automate a process we didn't yet fully understand. My only =20
> real regret is that we broke things too far too fast, but that is =20
> water under the bridge.

For the record (I'm just catching up with email from the last week on
vacation):

I used very small tools to blow up the trunk after doing the process
manually a few times and looking out for issues that had to be done. The
result was pretty homogenuous.

The general blow-up was pretty consistent and reliable as I also tested
all produced individual eggs with a buildbot (which isn't available
anymore unfortunately, I really want to get back to that) and used
projects like grok and our own projects to verify they are still working
with the eggs.

Christian

--=20
gocept gmbh & co. kg - forsterstrasse 29 - 06112 halle/saale - germany
www.gocept.com - [email protected] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development


--=-rip/HU3jFwNu/mwjENNT
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBHC5zndUt9X/gknwIRAt71AJ9VPYItewK0zzg/h2lwVNwWOLbnXQCfSJsd
Qim50L7DzNLx2M887oKyTbU=
=4nSr
-----END PGP SIGNATURE-----

--=-rip/HU3jFwNu/mwjENNT--


--===============0916314599==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline