Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 63933 invoked from network); 14 Feb 2007 01:42:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Feb 2007 01:42:10 -0000 Received: (qmail 88716 invoked by uid 500); 14 Feb 2007 01:42:18 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 88669 invoked by uid 500); 14 Feb 2007 01:42:17 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 88658 invoked by uid 99); 14 Feb 2007 01:42:17 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2007 17:42:17 -0800 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_10_20,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates 64.233.182.184 as permitted sender) Received: from [64.233.182.184] (HELO nf-out-0910.google.com) (64.233.182.184) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Feb 2007 17:42:07 -0800 Received: by nf-out-0910.google.com with SMTP id o25so513598nfa for ; Tue, 13 Feb 2007 17:41:46 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=J02fhPAchE5Mp5LYDiJU/1qPvwP3a9g3ePcpqpDFp9KYrNvstluZXULVsfO7zu8it6EuaVphxMx+E5HbcovLpkSAOLPgOlzt/lgiy5r5WflSbL3wCYN0XPsNGK711zok8hx2TOiVH4dKpHON2s7vkcsQ6hX8axR0vgblf43uMdw= Received: by 10.49.107.8 with SMTP id j8mr1316238nfm.1171417306247; Tue, 13 Feb 2007 17:41:46 -0800 (PST) Received: by 10.49.55.14 with HTTP; Tue, 13 Feb 2007 17:41:46 -0800 (PST) Message-ID: Date: Tue, 13 Feb 2007 20:41:46 -0500 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: [ApacheDS] Shall we upgrade to MINA 1.0.2 before releasing 1.0.1? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_38250_1235526.1171417306217" X-Google-Sender-Auth: 9d51df2e6c17db36 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_38250_1235526.1171417306217 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I think the MINA folks were going to release 1.0.2 shortly. We can easily upgrade to MINA 1.0.1 for ApacheDS 1.0.1 now. Should we wait until the MINA release? Trustin, how close is the MINA team towards releasing 1.0.2? Thanks, Alex ------=_Part_38250_1235526.1171417306217 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline I think the MINA folks were going to release 1.0.2 shortly.  We can easily upgrade to
MINA 1.0.1 for ApacheDS 1.0.1 now.  Should we wait until the MINA release?

Trustin, how close is the MINA team towards releasing 1.0.2?

Thanks,
Alex
------=_Part_38250_1235526.1171417306217--