Return-Path: X-Original-To: apmail-groovy-users-archive@minotaur.apache.org Delivered-To: apmail-groovy-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C0C3718FBA for ; Wed, 5 Aug 2015 08:28:36 +0000 (UTC) Received: (qmail 75153 invoked by uid 500); 5 Aug 2015 08:28:31 -0000 Delivered-To: apmail-groovy-users-archive@groovy.apache.org Received: (qmail 75118 invoked by uid 500); 5 Aug 2015 08:28:31 -0000 Mailing-List: contact users-help@groovy.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@groovy.incubator.apache.org Delivered-To: mailing list users@groovy.incubator.apache.org Received: (qmail 75108 invoked by uid 99); 5 Aug 2015 08:28:31 -0000 Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Aug 2015 08:28:31 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 06018C009C for ; Wed, 5 Aug 2015 08:28:31 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.108 X-Spam-Level: X-Spam-Status: No, score=-0.108 tagged_above=-999 required=6.31 tests=[KAM_LIVE=1, RCVD_IN_MSPIKE_H2=-1.108, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id gQrhTylrZwxA for ; Wed, 5 Aug 2015 08:28:22 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 98887205B9 for ; Wed, 5 Aug 2015 08:28:21 +0000 (UTC) Received: from [192.168.1.3] ([85.180.108.170]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0LhOvA-1Z0oqz0aLA-00mZOy for ; Wed, 05 Aug 2015 10:28:13 +0200 Message-ID: <55C1C9DE.2040407@gmx.org> Date: Wed, 05 Aug 2015 10:31:26 +0200 From: Jochen Theodorou User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: users@groovy.incubator.apache.org Subject: Re: Groovy Release Roadmap References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:GC9kxnnT/WY5HwotIBD/nMCeUD4evJ4A0wW0MqPCWr3HENNtDDS h1jLFGcxV38qSsEgRz9iQwdQmivx2tVXkTqSBqFYLyR0WPZfbN5wHRvP7VjwN8ADv7jdpK6 9l+PmuaoL9tz+735NvgFzdbj5AhFYkb5Q23TAWkuwzShSBWFWXXg7zxGoMy5aGcAA/e7qlR Y3Se6wfO/A5JydppaONKA== X-UI-Out-Filterresults: notjunk:1;V01:K0:lIDAVCy8fPs=:pWb81GmYEc7H6JjJrYwiUA uJ7lFHA+gyaFmNtzw/mN0Fi4NYQr8bcFk9fS9VHxjY6Yfuf+1aT03n4b+Y8kxt2H0hv4smrxr alo+zno1sXbOdqd/vb9svNt9K2ArJI/dzCP2rAFGAk7y+/3zeGy9qLt5TVV9ltR8gztt0sJIY I4a+Ov+xsGlvBrdA+JLb+sE0oKXAiOU7W6nm9GSic98TLv63zV3V7pnIzYix30hrWQ3SdBo9m w6ZKg0cmFqjfzcmHZZSDaKund/poNA/IoH5iXAUQMEVWg8FbPQgaRcB8yWYrLkT2prXPyn4d/ SPZcByp+y52F1R+s0IDRwCWW61r6U1Lr5OLZhB6J5FN4HSFs+yWMGLVnZ5SCYYK0Cu20zExqT nWToB1zmSoPlsWuJR1lImv32b0vWE0sa+QaVG3zOaiU8ONev0gAVCjeDimvRsaxm8a2ccEXWw 4mEPqb4xW7/fO+Ut7/G2QoKJM6N+h6kkV6F1LJGruAqJbvgKBfu853NBKY4V84fZAmSQguCn5 N4ajgK8CCXlvssmua6NRihy/MujSsaipUnQ/DO/zbtekjNo1RAL36Vsz8HUDjqTxcX2YJyHks 7LB+tHeE0xaR0T8Tv4zDwoJL52W1tVLO1y8sr0EmDG6ui0GkQe9QYJLTVM3wK9CdNb+3qYW0N vwQOHRpPqku4e30Pe+HKdokwtCGNoZl1cb87RsjUGelKXrbPPrQbsb6keLLot0qNy02o= Am 05.08.2015 03:52, schrieb Nicholas Grealy: > First of all, congratulations on the 2.4.4. release under the Apache > flag (3 weeks ago)! Great stuff. > > Where can I find out when future release dates of Groovy are planned > for? (Specifically, I'm interested in the release date for 2.5.X > ) > > I've had a look at the roadmap > , > and there isn't a planned date for the next release (2.4.5) or future > releases. I understand if processes are still in a state of flux, what > with the move to Apache etc (I'm happy to be patient). Am I looking in > the right place? Also, what is the trigger/process for setting release > dates? normally we do one bigger release per year and otherwise bugfix releases. That would mean normally we would plan to release 2.5.0 in early 2016, with several beta releases before... which we should probably start on soon. Bugfix releases, well we do them normally if one of 3 things happen: we got quite some issues resolved (50+), somebody asks for it or there was a longer period of time (like 3 months) without release But frankly all these are open points right now, because this was what we did before moving to apache and with having several full time developers. As for 2.5, why is it that you are asking for the release. What issue triggered that for you? bye blackdrag -- Jochen "blackdrag" Theodorou blog: http://blackdragsview.blogspot.com/