Date: Tue, 8 Feb 2005 04:51:44 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Mike Brown <mike@skew.org> Cc: freebsd-ports@freebsd.org Subject: Re: impending port removal date coincides with new release Message-ID: <20050208125144.GB77644@xor.obsecurity.org> In-Reply-To: <200502080917.j189H63J073918@chilled.skew.org> References: <200502080917.j189H63J073918@chilled.skew.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--p4qYPpj5QlsIQJ0K Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 08, 2005 at 02:17:06AM -0700, Mike Brown wrote: > The current release version of 4Suite, an XML & RDF toolkit for Python, i= s=20 > 1.0a4. If all goes well, we're going to release 4Suite 1.0b1 on Feb 15th. >=20 > The textproc/py-4suite port, years out of date and long broken, is schedu= led=20 > for deletion on Feb 18. I will have a port for 1.0b1 ready soon after=20 > release, maybe on the 15th or 16th, but obviously that would be cutting t= he=20 > approval window a bit close. >=20 > I could submit a 4Suite 1.0a4 port right now (it's done), just to keep th= e=20 > port from dying, but I would rather not have 1.0a4 floating around, if it= can=20 > be avoided. >=20 > What should I do? I think the simplest solution would be to just push the > removal date out by a couple of weeks. Is that an option? Yes. Thanks for your interest. Kris --p4qYPpj5QlsIQJ0K Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCCLXfWry0BWjoQKURAicJAKCE/fVpHQZ6h+1/dKKmfyw2wFucYACeKg5R m+5bftSORRNhnxiow027pq0= =FsNh -----END PGP SIGNATURE----- --p4qYPpj5QlsIQJ0K--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050208125144.GB77644>