--=-5kYtb76xiuEXdenIhSRI Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2003-02-04 at 09:09, Troy Dawson wrote: > Hi Seth, > I think it's a good idea. At some point you just have to diverge and go = for=20 > the python2 and rpm 4.2. But I have one comment. > When you do the breakoff, can you make it everything greater than 2.0 ins= tead=20 > of 1.0. That way, at some point, you can actually have a 1.0 release for= the=20 > python 1.x. rpm 4.0x. > I know that sounds trivial, but some people simply don't think a product = is=20 > usable until it hit's it's 1.0 release. It's a mental thing I know, but = it's=20 > in alot of people's minds that way. > You could also say then that the yum 1.0 goes with python 1, and yum 2.x = goes=20 > with python 2. I think that's how it'll go. I considered 1.0 vs 1.2 but <shrug> 6 of one, half dozen of the other Maybe I could start numbering towards more specific values of Pi No, Wait. that's been done. :) -sv =20 --=-5kYtb76xiuEXdenIhSRI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQA+QnuB1Aj3x2mIbMcRAndrAKCnYOwYOBG1qiZO7e3MGyvUP0q4jwCdH5xS 8pR/Rh1tYHEZfOS9i+9V3Vk= =4qlo -----END PGP SIGNATURE----- --=-5kYtb76xiuEXdenIhSRI--
