Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: etch-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of martijn.dashorst@gmail.com
 designates 209.85.212.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=EPRE9XFaXOIdegxCepe22ygkL4tFxqP3KlzCa0l9pCdoIUxYE355SDQrfu8l4dUg4Z
         aqugTxuUcxWpOY2fkT81e95gLhtcga8kU1jMa5Ea7zwoEPBvf3Vf+5kU6Bu51KRJdGnQ
         qUNnXhZcIqTpbT/hwQMqIM2HfdyCsDZ5SUKhE=
MIME-Version: 1.0
In-Reply-To: <66BD268F973E3544A665E5F503FB38B7057363DF02@DC01.bmw-carit.intra>
References: <AANLkTi=WdNvWzrY9nhA3F-578w=rFj_SAzy_4ktr3OEC@mail.gmail.com>
 <20100902053114.GA53798@dixson3.dyndns.org>
 <E3726195FF58A940A18095501E383752BDFCBE@xmb-sjc-215.amer.cisco.com>
 <AANLkTim_Vci83p0ykxLyUMSHUarPnx-UugBY80S5o4EV@mail.gmail.com>
 <66BD268F973E3544A665E5F503FB38B703A5A2CC4F@DC01.bmw-carit.intra>
 <AANLkTikV6veskFL5hjMG9WnWF1URb_JWy=b9AT5=HpQa@mail.gmail.com>
 <66BD268F973E3544A665E5F503FB38B705229957B6@DC01.bmw-carit.intra>
 <4C87BE3F.3050201@apache.org>
 <66BD268F973E3544A665E5F503FB38B70549863011@DC01.bmw-carit.intra>
 <AANLkTimbVa20tmBChDprSJUp3qoKgkp5mPQo=Nx+c7HJ@mail.gmail.com>
 <4C8E26B2.9030105@mac.com>
 <66BD268F973E3544A665E5F503FB38B7057363DF02@DC01.bmw-carit.intra>
From: Martijn Dashorst <martijn.dashorst@gmail.com>
Date: Tue, 14 Sep 2010 15:40:49 +0200
Message-ID: <AANLkTinERpM8E7EACkAJ6zieqhGDZukOo7eVLYbwPhFP@mail.gmail.com>
Subject: Re: [VOTE] Contents of Release 1.1
To: etch-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1

I don't think a vote was necessary, nor is there any procedure to be
followed, however it never hurts to ask to include something, or to
poll consensus on an issue. That said, if someone is willing to be a
release master, then they get all the leeway they need. If the release
master thinks that the C bindings should go with the release, then so
be it. If there's objection to doing so in 1.1, why not skip 1.1 and
go directly to release 1.2?

The ASF fosters meritocratic communities where merit is earned by doing.

Martijn

On Tue, Sep 14, 2010 at 11:57 AM, Holger Grandy
<Holger.Grandy@bmw-carit.de> wrote:
> Hi guys,
>
> since Scott is mentioning voting procedures, I would like to pick up that=
 point and start
> a vote regarding a upcoming release 1.1 of Etch. Vote will run for 72 hou=
rs until Friday.
>
> I propose that we publish Release 1.1 with the C binding implementation i=
ncluded
> in the next weeks (as stated in the mail below).
>
> Please vote:
> -1 : no, release 1.1 should not contain the C binding, because ...
> 0 =A0: I don't care
> +1 : Release 1.1 should be published with the C binding as described belo=
w
>
> ----
> +1 from me
>
> Regards,
> Holger
>
>
> -----Original Message-----
> From: scott comer [mailto:wert1y@mac.com]
> Sent: Montag, 13. September 2010 15:27
> To: etch-dev@incubator.apache.org
> Subject: Re: Future of Etch
>
> =A0well, much as martijn might wish otherwise, there are procedures for
> voting such a plan.
>
> i don't like two things:
>
> 1) please don't remove the tag.
>
> 2) why not proceed with the release 1.1 as is, and release 1.2 with c
> binding from trunk. less confusion.
>
> scott out
>
> On 9/13/2010 2:36 AM, Martijn Dashorst wrote:
>> On Fri, Sep 10, 2010 at 4:14 PM, Holger Grandy
>> <Holger.Grandy@bmw-carit.de> =A0wrote:
>>> We have seen an older mail regarding release 1.1. from April. I propose=
 we start over to prepare a release
>>> package in September and initiate a PMC vote regarding that when its re=
ady. Will create Jiras for that.
>>> Proposal: remove the old release 1.1 branch, merge etch-c into trunk, f=
ix bugs, create new release
>>> branch from trunk for 1.1
>> This sounds like a good plan. Go for it.
>>
>> Martijn
>
>


--=20
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8