Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of omuppi1@gmail.com designates
 209.85.220.178 as permitted sender)
MIME-Version: 1.0
Sender: omuppi1@gmail.com
In-Reply-To: <5E55D331-2433-4278-BC8A-F79F12284242@classsoftware.com>
References: <CFE69753.27CEE%aharui@adobe.com> <CFE9786B.236CC%pent@adobe.com>
 <2E8A70D2-0B58-438A-A84F-5E2660DFFFD4@classsoftware.com>
 <CACK5iZcPeynG_xedXEiwC0wgHygAUXbgtKbn2aBkB=VTdv-kBw@mail.gmail.com>
 <5E55D331-2433-4278-BC8A-F79F12284242@classsoftware.com>
From: OmPrakash Muppirala <bigosmallm@gmail.com>
Date: Mon, 14 Jul 2014 16:16:32 -0700
Message-ID: 
 <CACK5iZdzjUgw0_0gFQVGmpCjkiXMOJUoGG5TZLGtkvbadu9CPw@mail.gmail.com>
Subject: Re: [VOTE] Apache FlexJS 0.0.2 RC5
To: "dev@flex.apache.org" <dev@flex.apache.org>
Content-Type: multipart/alternative; boundary=047d7b342d30188d1d04fe2f7d2b

--047d7b342d30188d1d04fe2f7d2b
Content-Type: text/plain; charset=UTF-8

On Mon, Jul 14, 2014 at 4:00 PM, Justin Mclean <justin@classsoftware.com>
wrote:

> Hi,
>
> > It might be a regression, but is it really a release blocker?
> I don't think it's a release blocker but IMO we should be releasing better
> quality software especially if we want people to try and it and lend a hand
> to fix stuff.


It is a vicious cycle.  If we don't release often we risk losing the
community's interest.  We have been churning on these release candidates
for a quite a bit now.  We should resist the urge to fix every little issue
we find.


> Knowing how to compile it correctly helps (the instructions are currently
> misleading re FP 11.1) and there's no list of what works or what doesn't
> for the examples. We had the same discussion for the last release and
> nothing improved  since then.


Expecting one or two people to fix all this within a release is not
reasonable.  We need more people working on this.  Again, the key to
attracting more volunteers is to getting this SDK into their hands.

Thanks,
Om


> As with all releases if it gets the required 3 +1's (and more +1s than
> -1s) it can be released.
>
> >  IMO, we should log a JIRA ticket and address it in the next release.
> Already done see https://issues.apache.org/jira/browse/FLEX-34416
>
> Thanks,
> Justin

--047d7b342d30188d1d04fe2f7d2b--