Return-Path: Delivered-To: apmail-jakarta-oro-dev-archive@apache.org Received: (qmail 4852 invoked from network); 8 Jan 2002 18:18:52 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 8 Jan 2002 18:18:52 -0000 Received: (qmail 9320 invoked by uid 97); 8 Jan 2002 18:18:57 -0000 Delivered-To: qmlist-jakarta-archive-oro-dev@jakarta.apache.org Received: (qmail 9276 invoked by uid 97); 8 Jan 2002 18:18:56 -0000 Mailing-List: contact oro-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "ORO Developers List" Reply-To: "ORO Developers List" Delivered-To: mailing list oro-dev@jakarta.apache.org Received: (qmail 9264 invoked from network); 8 Jan 2002 18:18:56 -0000 Message-Id: <200201081819.g08IJGY09841@gandalf.savarese.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: oro-dev@jakarta.apache.org Subject: 2.0.5 release? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Jan 2002 13:19:15 -0500 From: "Daniel F. Savarese" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N The last set of fixes has been sitting in CVS for a while now. Since some interest has developed in adding some new features, I think it's a good time to package up a 2.0.5 maintenance release this week before adding anything to the head branch. Even though according to the Jakarta procedures only committers can vote for release, I'm probably the only active committer at this time (which kind of puts us in violation of Jakarta project rules, but that's for another discussion), so I guess it would be in the spirit of the rules if anyone who's submitted a patch and had it applied votes. I'm +1 for a 2.0.5 maintenance release. daniel -- To unsubscribe, e-mail: For additional commands, e-mail: