harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sian January" <sianjanu...@googlemail.com>
Subject Re: [general] Harmony M2 schedule
Date Mon, 11 Jun 2007 10:14:50 GMT
On 09/06/07, Mikhail Loenko <mloenko@gmail.com> wrote:
>
> 2007/6/7, Sian January <sianjanuary@googlemail.com>:
> > On 07/06/07, Mikhail Loenko <mloenko@gmail.com> 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]
> > >
> http://svn.apache.org/viewvc/harmony/standard/site/docs/m2.html?view=co
> > > >
> > > > I have a problem with the way the requirements are being stated for
> M2.
> > > >  Maybe it is just the terminology I'm uncomfortable with, that they
> are
> > > > 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
> the
> > > date.
> > >
> > > > M2 or drop some requirements?  I would suggest that instead we have
> > > > timeboxed stable development cycles, and plan what should get into
> each
> > > > stable milestone.
> > > >
> > > > I still haven't heard a good reason why these should be put into
> JIRA
> > > > titles either.  Can't we just agree that a JIRA should be in
> Milestone
> > > > '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
> sort
> > > out requirements (or goals) and see which bugs need to be fixed to
> meet
> > > 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.
> >
> >
> >
> > Just my two-pence-worth, but this seems like adding lots of extra
> > administrative work to end up with something that we're not sure we're
> going
> > to need.  Did anyone actually feel they needed this fine-grained detail
> in
> > JIRA when we put out M1?  I agree that it would be useful to be able to
> see
> > what bugs were fixed for a particular milestone or target bugs to a
> > milestone but I personally think going into any more detail than that is
> > unneccesary.
> >
> > I also think a week's code freeze seems quite long in proportion to a
> > 2-month release cycle (over 10% of the cycle), although that may just be
> me
> > :)
>
> If we have all the goals met then we may declare the frozen snapshot as
> our milestone build as soon as all the testing is done and move further.
> In this case it will be just 3% of the cycle :)
>
> But if there are critical bugs then we have time to fix them



Ok - that does seem to make sense, so there's a buffer if there are critical
bugs but development is not held up unless absolutely necessary.

Thanks,

Sian



> Thanks,
> Mikhail
>
>
> >
> > Regards,
> >
> > Sian
> >
> >
> > One more question:
> > > should the reqs (goals) be on website or wiki?
> > >
> > > Thanks,
> > > Mikhail
> > > >
> > > > Regards,
> > > > Tim
> > > >
> > >
> >
> >
> >
> > --
> > Unless stated otherwise above:
> > IBM United Kingdom Limited - Registered in England and Wales with number
> > 741598.
> > Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
> 3AU
> >
>



-- 
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

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