From dev-return-26088-apmail-mina-dev-archive=mina.apache.org@mina.apache.org Tue Nov 26 22:03:50 2013 Return-Path: X-Original-To: apmail-mina-dev-archive@www.apache.org Delivered-To: apmail-mina-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 836AB10B56 for ; Tue, 26 Nov 2013 22:03:50 +0000 (UTC) Received: (qmail 47739 invoked by uid 500); 26 Nov 2013 22:03:50 -0000 Delivered-To: apmail-mina-dev-archive@mina.apache.org Received: (qmail 47717 invoked by uid 500); 26 Nov 2013 22:03:50 -0000 Mailing-List: contact dev-help@mina.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@mina.apache.org Delivered-To: mailing list dev@mina.apache.org Received: (qmail 47708 invoked by uid 99); 26 Nov 2013 22:03:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2013 22:03:50 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates 74.125.82.49 as permitted sender) Received: from [74.125.82.49] (HELO mail-wg0-f49.google.com) (74.125.82.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 26 Nov 2013 22:03:43 +0000 Received: by mail-wg0-f49.google.com with SMTP id x12so5860091wgg.4 for ; Tue, 26 Nov 2013 14:03:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ahL6IhHZu6qucbl8I+WP84eYDuZb0W/LR+v9loT1cBY=; b=s72+1uJC107BFn/QwEa86yCJraITS13UbnhECgmSnOS+qZs8Kjff18gJmXNfPgHCP6 f4QReT43VM8kfrwNVYBBvEXrgkB+gtW5Jk0iSwURq2F1VgNvJpkQ2pLfWBk7AqrEw10Z KviDglOcK7eSK6bOzwR4wecSZSpq6Na0pmUz3jFqCmpeyxqXrYc63hR3hsthHJdMtsPM 8GDmNAPVtxPS7E/fiX0/ukhpSxOZWGwMfdQKckLCoS32+hF2d2Hf7BTTIBSRu0VfMMZf zmkgyzeTAv2T59tATtEYsIuiHs5PX7Ynu9wQJe6BtVRnoQRLWFpin7pOp9xK6Stex+vl DQpg== X-Received: by 10.180.72.243 with SMTP id g19mr15358557wiv.62.1385503403621; Tue, 26 Nov 2013 14:03:23 -0800 (PST) Received: from new-host-3.home (AMontsouris-651-1-223-20.w92-140.abo.wanadoo.fr. [92.140.70.20]) by mx.google.com with ESMTPSA id pi6sm64696461wic.3.2013.11.26.14.03.22 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 26 Nov 2013 14:03:22 -0800 (PST) Message-ID: <52951AA9.8000405@gmail.com> Date: Tue, 26 Nov 2013 23:03:21 +0100 From: =?UTF-8?B?RW1tYW51ZWwgTMOpY2hhcm55?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: dev@mina.apache.org Subject: Re: Big mess in 2.0 References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Le 11/26/13 10:40 PM, Jeff MAURY a écrit : > Hello, > > I'm restoring my Mina development environment after my disk crash. > I noticed we now have two branches for 2.0, the 2.0 and 2.0.8. > It seems most of the updates has been done in 2.0. > So I think we shoud clean up this situation. > I will propose: > > - merge 2.0.8 into 2.0 +1 > - put 2.0.8 in read only: don't know if Infra can do it, but I don't > like deleting something on the server 2.0.8 is useless. Once it gets merged into 2.0, why should we keep it ? All in all, we can also just apply the few modifications done on 2.0.8 (currently, only 2) We also need to get a 2.0.8 release cut pretty soon, as a few critical bugs have been fixed in this branch. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com