incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Om <bigosma...@gmail.com>
Subject Re: Flex 4.0.0 release questions (was Re: [VOTE] Release Apache Flex 4.8.0)
Date Sat, 30 Jun 2012 16:36:38 GMT
On Fri, Jun 29, 2012 at 10:31 PM, Alex Harui <aharui@adobe.com> wrote:

>
>
>
> On 6/29/12 9:53 PM, "Om" <bigosmallm@gmail.com> wrote:
>
> > (Removing the [VOTE] tag as we have started discussing stuff)
> >
> > Does Apache have a practice of releasing a beta?  Or do we release 4.8.0
> > and as things comes up we keep cutting 4.8.1, 4.8.2, etc. as releases?
> >
> > It looks like we are releasing a beta out to the public, but we are not
> > officially calling it a beta.
> >
> Why do you think it is a beta?
>
>
Mostly because we have not found any major issues yet.  I am not sure if
its because we did a lot of testing and came up with very few bugs or if we
havent done enough testing.  I know builds have been constantly updated
with some of us emailing out problems they faced.  But what level of
clarity do we have on how much testing was done?   Maybe if we had people
piping up with - "I tested it, it looks fine" emails, I wouldnt be so
worried.

Also, I am worried about pushing out a public release and then people pound
on it and we start finding bigger issues.  We probably need to have a plan
for when something like that happens, right?

The best way to test a parity release is to take a project that was
compiled with Adobe Flex 4.6 and test it with Apache Flex 4.8 to see if
something breaks.  I dont know if we have any such designated projects in
our trunk we constantly test each build with.  This means that most of the
testing on the 4.8 release will happen on end users' projects.

Calling it a beta is a more cautious approach, IMHO.  Especially given the
fact that this Apache Flex's first release.

Thanks,
Om

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message