Return-Path: X-Original-To: apmail-commons-dev-archive@www.apache.org Delivered-To: apmail-commons-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 23047981A for ; Sun, 23 Oct 2011 15:43:07 +0000 (UTC) Received: (qmail 64091 invoked by uid 500); 23 Oct 2011 15:43:06 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 64007 invoked by uid 500); 23 Oct 2011 15:43:06 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 63999 invoked by uid 99); 23 Oct 2011 15:43:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Oct 2011 15:43:06 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of simone.tripodi@gmail.com designates 209.85.161.171 as permitted sender) Received: from [209.85.161.171] (HELO mail-gx0-f171.google.com) (209.85.161.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Oct 2011 15:42:59 +0000 Received: by ggnv5 with SMTP id v5so7476753ggn.30 for ; Sun, 23 Oct 2011 08:42:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=KXS+OlXJqbIfgJrNF5/8sd00fb/iEO9o1yNrc3SmQS8=; b=nnxyeHFcxjrOtkreeaGiNyyuKzKFZue1krugs2C3fy+6IkroSsCkBS4uYI/P6rMf4n LtGHNoQ1XmClza4c/LzlFMlqasHyrNlBU2exrOU74MNXkgSoDbgsTBlIC08xSPjp4avh 0ys20Vq1+feM+pscsEzxopSU7D9ITF7kEAvjs= MIME-Version: 1.0 Received: by 10.150.199.9 with SMTP id w9mr18019386ybf.71.1319384558697; Sun, 23 Oct 2011 08:42:38 -0700 (PDT) Sender: simone.tripodi@gmail.com Received: by 10.150.96.13 with HTTP; Sun, 23 Oct 2011 08:42:38 -0700 (PDT) In-Reply-To: References: <4EA0A13F.1040009@apache.org> <4EA14354.8020605@apache.org> Date: Sun, 23 Oct 2011 17:42:38 +0200 X-Google-Sender-Auth: 2mnLGH5lk9gJoEoQQmPXBzhNEMM Message-ID: Subject: Re: [VOTE][RESULT] Release Apache Commons Functor 1.0 based on RC1 From: Simone Tripodi To: Commons Developers List , adrian@cumiskey.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Adrian, Of course, we still need a lot of work before next RC, your contribution would be more then welcomed! Hope to hear from you soon, have a nice day! All the best! Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Sun, Oct 23, 2011 at 5:26 PM, Adrian Cumiskey wrote: > When I take a look at JIRA, Functor currently has only two open issues, o= ne > minor and one trivial. =C2=A0It would be good to capture all the outstand= ing work > items that people feel are preventing a new RC. =C2=A0I would also be hap= py to > contribute to improving Functor. > > Cheers, Adrian. > > On 23 October 2011 06:46, Simone Tripodi wrote= : > >> Hi all guys, >> Since 72 hours passed I'm declaring this vote as closed and NOT passed >> with only 2 positive votes from PMCs: >> >> =C2=A0* Matt Benson >> =C2=A0* Simone Tripodi (implicit) >> >> no other votes were cast. >> >> We will continue working towards a new RC to submit. >> >> Thanks to all for your support and patience! >> Have a nice weekend, all the best! >> Simo >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> >> >> On Fri, Oct 21, 2011 at 6:36 PM, sebb wrote: >> > On 21 October 2011 16:04, Matt Benson wrote: >> >> On Fri, Oct 21, 2011 at 5:27 AM, sebb wrote: >> >>> On 21 October 2011 11:03, Emmanuel Bourg wrote: >> >>>> Le 21/10/2011 11:10, Simone Tripodi a =C3=A9crit : >> >>>> >> >>>>> So, as you proposed, would be reasonable to drop the 1.0 and decid= e >> >>>>> upon for a 0.1 as current release? >> >>>> >> >>>> Yes, or a 1.0-beta with clear indications that this is a preview >> intended to >> >>>> gather user feedback. >> >>> >> >>> I don't think it's ready for beta status yet. >> >>> >> >>> But - is there any pressing need to make a release? >> >> >> >> The most immediate thing is that [proxy] 2 needs a unary predicate. >> >> It becomes ridiculous for every component we have to define such a >> >> basic interface in a different way. =C2=A0So [proxy] 2 can never be >> >> released without a [functor] release, etc. >> >> >> >>> >> >>> For developer testing, a snapshot release is probably sufficient, an= d >> >>> can be updated very quickly - no need for a vote. >> >> >> >> This is indeed sufficient for the immediate future, but again, become= s >> >> *insufficient* soon enough. =C2=A0I don't personally see what purpose= is >> >> served by a 0.x release, but I have to say it's frustrating to work o= n >> >> a component and only when a release is proposed does everyone who >> >> couldn't have cared less before come out of the woodwork to suddenly >> >> find design issues (issues such as undocumented @SuppressWarnings com= e >> >> down to personal opinion and I would personally argue they shouldn't >> >> be release blockers, particularly as more often than not the >> >> justification is obvious). >> > >> > That entirely depends on circumstances; I've seen lots of cases where >> > they are just used to silence warnings, with no attempt to solve the >> > cause of the warning. >> > In some (perhaps rare) cases, fixing the warning may point to a >> > fundamental design issue, and/or need to change the API. >> > >> >> For those of you who have suddenly decided >> >> you care about this component: =C2=A0if we discuss and resolve the >> >> fundamental design concerns (i.e. no promises beyond reaching >> >> consensus), can you stay engaged long enough for us to get this >> >> wrapped up? >> > >> > I'm happy to contribute if I can; I had not realised that an RC was >> > imminent otherwise I might well have dived in earlier. >> > >> > There are too many components to follow every single one all the time; >> > besides, things are often in a state of flux between releases - >> > there's no point dotting i's and crossing t's if the entire paragraph >> > is about to be rewritten. Been there, done that in other projects. >> > >> >> Matt >> >> >> >>> >> >>>> >> >>>> Emmanuel Bourg >> >>>> >> >>>> -------------------------------------------------------------------= -- >> >>>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> >>>> For additional commands, e-mail: dev-help@commons.apache.org >> >>>> >> >>>> >> >>> >> >>> --------------------------------------------------------------------= - >> >>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> >>> For additional commands, e-mail: dev-help@commons.apache.org >> >>> >> >>> >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> >> For additional commands, e-mail: dev-help@commons.apache.org >> >> >> >> >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> > For additional commands, e-mail: dev-help@commons.apache.org >> > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org >> For additional commands, e-mail: dev-help@commons.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org