Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <008201c56326$a2db5f40$34b20704@oemcomputer>
From: "Bill Barker" <wbarker@wilshire.com>
To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Subject: What to do now
Date: Fri, 27 May 2005 18:43:18 -0700
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----------=_1117244562-31832-391"

------------=_1117244562-31832-391
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Now that we are officially a TLP (and, by the way, congrats Remy :), what is 
the migration strategy?

I'm assuming that we'll need to do a new 'ci' on all of what once was 
jakarta-tomcat*, but did jakarta-servletapi* and jakarta-watchdog* follow 
us?


This message is intended only for the use of the person(s) listed above as the intended recipient(s), and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended recipient, you may not read, copy, or distribute this message or any attachment. If you received this communication in error, please notify us immediately by e-mail and then delete all copies of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet is not secure. Do not send confidential or sensitive information, such as social security numbers, account numbers, personal identification numbers and passwords, to us via ordinary (unencrypted) e-mail.


------------=_1117244562-31832-391
Content-Type: text/plain; charset=us-ascii

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
------------=_1117244562-31832-391--