Return-Path: Delivered-To: apmail-incubator-etch-dev-archive@minotaur.apache.org Received: (qmail 7511 invoked from network); 27 Jan 2009 22:48:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jan 2009 22:48:55 -0000 Received: (qmail 58606 invoked by uid 500); 27 Jan 2009 22:48:55 -0000 Delivered-To: apmail-incubator-etch-dev-archive@incubator.apache.org Received: (qmail 58591 invoked by uid 500); 27 Jan 2009 22:48:55 -0000 Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: etch-dev@incubator.apache.org Delivered-To: mailing list etch-dev@incubator.apache.org Received: (qmail 58579 invoked by uid 99); 27 Jan 2009 22:48:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jan 2009 14:48:55 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of hedhman@gmail.com designates 74.125.44.154 as permitted sender) Received: from [74.125.44.154] (HELO yx-out-1718.google.com) (74.125.44.154) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jan 2009 22:48:46 +0000 Received: by yx-out-1718.google.com with SMTP id 36so2652086yxh.0 for ; Tue, 27 Jan 2009 14:48:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=L+9yAvIr8P4C0NcOgkgvy512r9C+gcor19xeIwF90rw=; b=VkwBxHZPFi1FZ+1S+HcfkxLMY3cp4GI0kik8jEnspeec5eyizbcwtCzuUsuy0lZcoN zRty6XZi3Vl5jL0uU3nezFK84FnAZFUDbWRikn1QY71mRrr8r+Yr67bI1SBiISl2rPVQ cbOmVWzT7ScxytvpiFgZzoSbcJ5uee/olKG5I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=vpphUIST1YASqG2MiKVsXVe5Kx2wlagc12jq6SoDkh1MamxtE5PUghdgmtiCFHx4kH IyhuRpQAPxT4iq0DMwpSuAx6MAKWugs1OkYA/gUcuzE9gvSI1hcVxXQ6cw1PVlQ/7fYA eGJJYPGm9/a7D15u9BmsV2ULviUGUFoxeasW4= MIME-Version: 1.0 Sender: hedhman@gmail.com Received: by 10.100.119.17 with SMTP id r17mr377056anc.61.1233096505841; Tue, 27 Jan 2009 14:48:25 -0800 (PST) In-Reply-To: <497F8030.9030207@cisco.com> References: <497F8030.9030207@cisco.com> Date: Tue, 27 Jan 2009 23:48:25 +0100 X-Google-Sender-Auth: 7658c5409f296c53 Message-ID: Subject: Re: branching etch for release 1.0.2, trunk is now release 1.1 From: Niclas Hedhman To: etch-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Tue, Jan 27, 2009 at 10:44 PM, scott comer (sccomer) wrote: > no other planning for 1.1 has occurred yet. to kick the ball, ideas for 1.1: > > c binding (nearly done) > python binding (in progress) > reference etch services (naming, configuration, authentication, logging, > router) > high performance transport using selectors (ETCH-10, ETCH-20) > interoptester (ETCH-15) Well it depends on what is a reasonable timeline. "Release Early, Release Often" is a mantra at ASF, although not all projects stick to it. So, if I were in your seat, I would take all the low hanging fruits and kick out a 1.1 release in say 4-6 weeks. Until then, hopefully some more ideas and work will approach 'low hanging', rinse and repeat. Personally, I hope to get enough time to supply a patch for 'dynamic hook', once I am back @ home. Probably take a few laps of questions, trial and error to get it right... Cheers Niclas -- http://www.qi4j.org - New Energy for Java