Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of alexey.a.petrenko@gmail.com
 designates 66.249.92.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=VJUgTbTCBbH6MX1KivqIhp3C8lI/Ity59JNNcOzrMFYa8ZxFQbXekt4O1A3WFEqrc7P/ukVl0/v0fgscEbVgRX2FTbZzevrCFUFkVB6YqUHAVZmuNfXJYJO6BSN0+DW1koB5djiN4d7KOhOwAE4jgMYDudBSAo6/rG+GRJq3o8o=
Message-ID: <c3755b3a0703050509u6e939144u85d4d8863d4c9ea8@mail.gmail.com>
Date: Mon, 5 Mar 2007 16:09:23 +0300
From: "Alexey Petrenko" <alexey.a.petrenko@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [general] Harmony Q2 release requirements
In-Reply-To: <906dd82e0703050053j19350331w9376df0c3d3331ad@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <906dd82e0703050053j19350331w9376df0c3d3331ad@mail.gmail.com>

2007/3/5, Mikhail Loenko <mloenko@gmail.com>:
> According to our high-level roadmap [1] we were going to make our
> first release in Q2. Let's define what we would like to see in our Q2
> release. If there are no objections let's discuss what we want that
> release being able to do.
>
> I suggest that we focus on stability measured by being able to
> successfully run a few solid applications and by pass rates for the
> test suites.
> So, I think in Q2 we should 1) run reasonable set of applications 2)
> have reasonable testing infrastructure and 3) pass reasonable set of
> test suites.
>
> Though we will be happy to accept all the patches that fix existing
> problems or add missing functionality, I suggest that people who hang
> around will focus on those scenarios that we will choose here
>
> Objections? :)
No objections! :)
We definitely need a milestone since milestones helps to keep us and
Harmony in good shape.

>
> If there are no objections again, I'd like to propose that we will target:
>
> 1) keeping all the enabled apps in the "up" state
> (we will create a list of enabled apps and put them all into cruise control)
>
> 2) running 2-3 open source server-side software
>
>
> 3) running 2-3 open source developers tools
>
>
> 4) setting up necessary testing infrastructure and having near 100%
> pass rates for the suites we have
>
>
> 5) what about commercial software? Some time ago we agreed that it's
> OK to report failures/regression of commercial software. Should we
> have them in the "requirements" to our Q2 release?

I think that we also need performance targets: run some benchmarks and
demonstrate reasonable results.
We are using Dacapo and SciMark now [1].

Do we need some additional benchmarks? And what will the reasonable
target results?

> Since currently the most stable platform is Windows/IA32 I suggest
> that Harmony Q2 will be released on that specific platform
+1

SY, Alexey

[1] http://harmony.apache.org/performance.html