harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Morozova, Nadezhda" <nadezhda.moroz...@intel.com>
Subject RE: [general] Harmony M2 schedule
Date Fri, 08 Jun 2007 11:18:54 GMT
>> One more question:
>> should the reqs (goals) be on website or wiki?
>I'd expect them to be on the wiki, but whatever.

+1. Wiki can give the flexibility of updating/discussing requirements
and their labels, and we could also store key points of the M2
discussion there. I think we did use Wiki to summarize dev-list
discussions before. 

>-----Original Message-----
>From: Tim Ellison [mailto:t.p.ellison@gmail.com]
>Sent: Thursday, June 07, 2007 5:12 PM
>To: dev@harmony.apache.org
>Subject: Re: [general] Harmony M2 schedule
>Mikhail Loenko wrote:
>> 2007/6/7, Tim Ellison <t.p.ellison@gmail.com>:
>>> Mikhail Loenko wrote:
>>> > I've added new requirements from this thread to [1,2]
>>> >
>>> > I've also put names of the requirements.
>>> > We may use these names in comments to JIRAs to simplify search.
>>> >
>>> > Please comment
>>> >
>>> > Thanks,
>>> > Mikhail
>>> >
>>> > [1] http://harmony.apache.org/m2.html
>>> > [2]
>>> I have a problem with the way the requirements are being stated for
>>>  Maybe it is just the terminology I'm uncomfortable with, that they
>>> being stated as 'requirements' and not 'goals'.
>>> What happens if these requirements are not met?  Do you slip the
date of
>> It's probably just the terminology. No, I'm not suggesting slipping
>> date.
>Ok, then I'm fine with the idea, and apologies for the
>  To my ear, a 'requirement' is mandatory/necessary, whereas a 'goal'
>an aim/direction.
>Having goals and themes that we work towards for the milestones is
>reasonable.  People will work on whatever their 'itch' dictates, but it
>is fine to allow people to declare what they are working towards.  Just
>to be clear, we would not stop people working on a problem because it
>does not fit in with a written goal.
>>> M2 or drop some requirements?  I would suggest that instead we have
>>> timeboxed stable development cycles, and plan what should get into
>>> stable milestone.
>>> I still haven't heard a good reason why these should be put into
>>> titles either.  Can't we just agree that a JIRA should be in
>>> 'X' or not?  Are you looking to group the JIRA issues into themes?
>> I did not talk about the titles, I suggested some way to be able to
>> out requirements (or goals) and see which bugs need to be fixed to
>> some specific goal.
>> I guess that our goals will be quite aggressive and we probably won't
>>  meet all of them. And if 3 days before milestone I see that 100 bugs
>> left and to meet goal N I need to fix one bug and to meet goal M I
>> need to fix 10 bugs I'll probably start with that only bug necessary
>> to meet the goal N. For that reason I need to be able to find bugs
>> affecting reqs (goals). I suggest that we use reg (goal) name in
>> comments, so that we can easily find which JIRA issues impact this
>> specific req.
>We welcome JIRAs from any Harmony user, so creating a new issue or
>reading an existing issue should not become burdened with undue
> A comment that an issue, for example, "blocks running a simple Tomcat
>scenario" makes sense to everyone, but a comment saying "M2_APP4" is
>just lingo.
>I wonder what is the best way of marking a JIRA issue so we can 'query
>by goal' without having to embed unreadable tags?
>Maybe open a JIRA for the 'run a simple Tomcat scenario' and make it
>dependent upon JIRAs that block that success.  Just thinking
>other ideas?
>> One more question:
>> should the reqs (goals) be on website or wiki?
>I'd expect them to be on the wiki, but whatever.

View raw message