Return-Path: X-Original-To: apmail-groovy-dev-archive@minotaur.apache.org Delivered-To: apmail-groovy-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B952C18685 for ; Sun, 13 Mar 2016 16:52:33 +0000 (UTC) Received: (qmail 56201 invoked by uid 500); 13 Mar 2016 16:52:33 -0000 Delivered-To: apmail-groovy-dev-archive@groovy.apache.org Received: (qmail 56164 invoked by uid 500); 13 Mar 2016 16:52:33 -0000 Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@groovy.apache.org Delivered-To: mailing list dev@groovy.apache.org Received: (qmail 56149 invoked by uid 99); 13 Mar 2016 16:52:33 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Mar 2016 16:52:33 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id BE7BA180315 for ; Sun, 13 Mar 2016 16:52:32 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.198 X-Spam-Level: * X-Spam-Status: No, score=1.198 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx2-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id YwDHVeWhX3Kg for ; Sun, 13 Mar 2016 16:52:31 +0000 (UTC) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com [209.85.220.172]) by mx2-lw-eu.apache.org (ASF Mail Server at mx2-lw-eu.apache.org) with ESMTPS id 1DDA55FB2D for ; Sun, 13 Mar 2016 16:52:30 +0000 (UTC) Received: by mail-qk0-f172.google.com with SMTP id s5so66566943qkd.0 for ; Sun, 13 Mar 2016 09:52:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=UDwYL0XWj+ft+hFeMxvnm7QQZQKqPkfJWWls6pTYs3w=; b=gawXy3YC3n7T4/fYlK5KIgyaC7pDQEcpn1LiJKXwpt0ebDnpgGMyosjaIZ1N3lTObI G+RxzsQk+0eJ3mBzyj2JysasCcYUU5yvIZj1T2T2BbJv+Xmei2ADLSPg0qe1WAHZlJFT PQ5Q//7OUGeisEYHPGkNCk2tw3jzAfPbp+0is3KBw/R5z7446xV4nW27U+jj/38cz0kt Esa8Z4E261HHTgzbm3AS89j7KQSW3dKMR4U86mwGsHXjrT/uT/knLrP3YLI5weSr1t2w d8tBVwNQPEouRL7M6riDGI4xhc/kGmL47KOcO4c+low7VQwcgZZ5Z6PiHeTHSh5xpS+B QSxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=UDwYL0XWj+ft+hFeMxvnm7QQZQKqPkfJWWls6pTYs3w=; b=KUnCXnt85lFAqX4qY5LlX9Do0DeMXp0Npl8t/TpwwZiAQmrWiFzrEf/my7IK2UwtOs x8tfYXjXQ0pcu5IiDDV81y2/ySGg0TkGwmb73B0EDuRT/5loJDyqDmFGW4TCoLwXqte0 A/4bkeUw5D64X5njU7dSdsuDPaDdCPwrFYfZCjDBdmJHyibHZ4li6IZuH9RRWyCW4DGq tNBhJnxbUHAr4AZr9dyjEUloWnuUHcBIaJUcSIr0j8IF7F9Jw1wqMMf1UM/k6h9RLLZo K83OqfLqjtvzo1yPqBUL6f/rEMdb4gsJ7LUHVcsoH+S56oG0cDL4pFOctPkUHdTBvGAR Vj7Q== X-Gm-Message-State: AD7BkJJsCkE7kEugdNFZgALnnJ5TA8uOM9W7DKamVsTyqyNOwnqMS76ao+LzWU35jb1wuFQkkPOz+QPBLSaUVA== MIME-Version: 1.0 X-Received: by 10.55.76.73 with SMTP id z70mr24740953qka.105.1457887949233; Sun, 13 Mar 2016 09:52:29 -0700 (PDT) Received: by 10.55.158.207 with HTTP; Sun, 13 Mar 2016 09:52:29 -0700 (PDT) In-Reply-To: References: <56DBFA6D.8030004@gmx.net> <96C5BE75-63F1-4895-825D-5CCCA0365540@cs.vassar.edu> Date: Sun, 13 Mar 2016 12:52:29 -0400 Message-ID: Subject: Re: Release 2.5 Beta? From: Shil Sinha To: dev@groovy.apache.org Content-Type: multipart/alternative; boundary=001a114a6bda5624e1052df0fd31 --001a114a6bda5624e1052df0fd31 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable > > I think it's a bit of a problem, still, when it's really that particular > feature which is in beta, and that we'll want users to test. Without > knowing it's there and how to use it it's going to be hard to have feedba= ck. Agreed, it would be strange to not have any documentation for the focal point of a release. Are there any external references which we could direct users to? Not from within the repo itself, but when promoting the release elsewhere e.g. Twitter. On Sun, Mar 13, 2016 at 8:49 AM, C=C3=A9dric Champeau wrote: > So does everyone agree that we should release the beta even if it's > missing docs for macros? I think it's a bit of a problem, still, when it'= s > really that particular feature which is in beta, and that we'll want user= s > to test. Without knowing it's there and how to use it it's going to be ha= rd > to have feedback. > > 2016-03-13 0:56 GMT+01:00 Suderman Keith : > >> >> On Mar 12, 2016, at 12:17 PM, Guillaume Laforge >> wrote: >> >> Let's go with mushroom, for a change :-) >> >> >> +1 >> >> >> On Sat, Mar 12, 2016 at 5:32 PM, C=C3=A9dric Champeau < >> cedric.champeau@gmail.com> wrote: >> >>> >>> >>> 2016-03-12 0:05 GMT+01:00 Nicholas Grealy : >>> >>>> Looks like it's just you and me, Pascal! >>>> >>>> Just some questions for the broader dev community: >>>> >>>> - Who can perform the release? - C=C3=A9dric looked like he single >>>> handedly pushed out version 2.4.6 - can we ask him to prepare the 2= .5 beta >>>> release? >>>> >>>> >>> Until we've switched to a new release process, it's still easier if I d= o >>> it, yes. >>> >>> >>>> >>>> - >>>> - Is there anything outstanding for a 2.5 beta release? - Whoever's >>>> we're waiting on, can we get an update? >>>> >>>> >>> There are lots of outstanding issues, that's why it's a beta. In >>> particular, the new (exciting!) macro stuff is not documented, nor the = AST >>> matcher complete. It's a super nice feature that deserves polishing. Pl= us, >>> there are some decisions to be made with regards to applying the global >>> `macro` AST xform globally or not, in particular with groovy-all. We ca= n >>> solve this after the beta, for sure, but we need to think about it. >>> >>>> >>>> - >>>> - Do we need a VOTE thread for a beta release? >>>> >>>> >>> Yes, it's a release. We can call it "beta", "rc" or "mushroom", it's a >>> release anyway :) >>> >>> Cheers! >>> >>>> >>>> - >>>> >>>> >>>> Kind regards, >>>> Nick >>>> >>>> On Mon, 7 Mar 2016 at 22:52 Nicholas Grealy >>>> wrote: >>>> >>>>> +1 >>>>> >>>>> On Sun, 6 Mar 2016 20:37 Pascal Schumacher >>>>> wrote: >>>>> >>>>>> Hello everybody, >>>>>> >>>>>> as far as I remember there was wide support for releasing a 2.5 beta >>>>>> in >>>>>> the "Release 2.4.6 and 2.5.0-beta?" discussion. >>>>>> >>>>>> The release announcement for 2.4.6 contained the sentence "... be >>>>>> prepared for a 2.5.0-beta release soon!". Tomorrow that will be two >>>>>> weeks ago, so I think we should make some plans when we start the >>>>>> release vote and who will be able to serve as a release manager. >>>>>> >>>>>> What do you think? >>>>>> >>>>>> Cheers, >>>>>> Pascal >>>>>> >>>>> >>> >> >> >> -- >> Guillaume Laforge >> Apache Groovy committer & PMC Vice-President >> Product Ninja & Advocate at Restlet >> >> Blog: http://glaforge.appspot.com/ >> Social: @glaforge / Google+ >> >> >> >> ------------------------------ >> Research Associate >> Department of Computer Science >> Vassar College >> Poughkeepsie, NY >> >> > --001a114a6bda5624e1052df0fd31 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I think = it's a bit of a problem, still, when it's really that particular fe= ature which is in beta, and that we'll want users to test. Without know= ing it's there and how to use it it's going to be hard to have feed= back.

Agreed, it would be strange to= not have any documentation for the focal point of a release. Are there any= external references which we could direct users to? Not from within the re= po itself, but when promoting the release elsewhere e.g. Twitter.

On Sun, Mar 13,= 2016 at 8:49 AM, C=C3=A9dric Champeau <cedric.champeau@gmail.com<= /a>> wrote:
So= does everyone agree that we should release the beta even if it's missi= ng docs for macros? I think it's a bit of a problem, still, when it'= ;s really that particular feature which is in beta, and that we'll want= users to test. Without knowing it's there and how to use it it's g= oing to be hard to have feedback.

2016-03-13 0:= 56 GMT+01:00 Suderman Keith <suderman@cs.vassar.edu>:

On Mar 12, 2016, at 12:17 PM, Guill= aume Laforge <gl= aforge@gmail.com> wrote:

Let's go= with mushroom, for a change :-)

+1


On Sat, Mar 12, 2016 at 5:32 P= M, C=C3=A9dric Champeau <cedric.champeau@gmail.com> = wrote:


2016-03-12 0:05 GMT+01:0= 0 Nicholas Grealy <nickgrealy@gmail.com>:
Looks like it's just you and m= e, Pascal!

Just some questions for the broader dev= community:
  • Who can perform th= e release? -=C2=A0C=C3=A9dric looked like he single handedly pushed = out version 2.4.6 - can we ask him to prepare the 2.5 beta release?

Until we've switche= d to a new release process, it's still easier if I do it, yes.
=C2=A0
  • Is there anything outstanding for= a 2.5 beta release? - Whoever's we're waiting on, can we get an up= date?

There a= re lots of outstanding issues, that's why it's a beta. In particula= r, the new (exciting!) macro stuff is not documented, nor the AST matcher c= omplete. It's a super nice feature that deserves polishing. Plus, there= are some decisions to be made with regards to applying the global `macro` = AST xform globally or not, in particular with groovy-all. We can solve this= after the beta, for sure, but we need to think about it.=C2=A0
=

  • Do we need a VOTE thread for a beta release?

Yes, it's a r= elease. We can call it "beta", "rc" or "mushroom&q= uot;, it's a release anyway :)

Cheers!=C2=A0

    • =

Kind regards,
Nick
=
On Mon, 7 Mar 2016 at 22:52= Nicholas Grealy <nickgrealy@gmail.com> wrote:

+1


On Sun, 6 Mar 2016 20:37 Pa= scal Schumacher <pascalschumacher@gmx.net> wrote:
Hello everybody,

as far as I remember there was wide support for releasing a 2.5 beta in
the "Release 2.4.6 and 2.5.0-beta?" discussion.

The release announcement for 2.4.6 contained the sentence "... be
prepared for a 2.5.0-beta release soon!". Tomorrow that will be two weeks ago, so I think we should make some plans when we start the
release vote and who will be able to serve as a release manager.

What do you think?

Cheers,
Pascal




--
Guillaume Laforge
Apache Groovy committer & PMC Vice-Pr= esident
Product Ninja & Advocate at Restlet

Blo= g:=C2=A0http://g= laforge.appspot.com/
Social: @glaforge=C2=A0/ Google+
<= /div>

------------------------------
Research Associate
Department of C= omputer Science
Vassar College
Poughkeepsie, NY



--001a114a6bda5624e1052df0fd31--