linaro-project-management team mailing list archive

[James Westby <james.westby@xxxxxxxxxx>]

Hi,

Here is what I took from our discussion yesterday:

Blueprints are somewhat lacking for our needs (such as having no advanced
search interface), and workitems are even more lacking.

We have the ability to use bugs linked to blueprints rather than
workitems, and could have linaro switch to using that exclusively,
rather than the whiteboard approach.

However, there are a few things that would have to change to allow that
to happen.

Firstly we would have to convert all the whiteboard workitems to bugs,
which we can do fairly easily with an API script. We can also make
something like that script available long term in order to allow for
engineers to easily file the bugs they need when creating a new spec.

This is something from 2 days to 2 weeks work, depending on what we want
to provide long-term.

If we do this there are further changes that we would like to have, such
as

  - Search for bugs attached to a blueprint
  - Reassign bugs from a package to a project
  - Displaying status of bugs on blueprint pages
  - Displaying milestone target of bugs on blueprint pages

If we decide to pursue this I will ensure all those bugs are filed and
attempt to escalate them through the launchpad stakeholder process.

In addition there is a desire to add effort estimation and recording to
bugs. Rob estimated this to be 1-2 weeks work, which the Infrastructure
team can take on if it is a high priority for Linaro.

Rob will draft the LEP for this, and ask for your input (LEP is
Launchpad's term for their specs)

I have just created a meeting tomorrow afternoon with the techleads to
discuss these issues.

I would like you to prepare a pitch to get agreement in principle from
them to pursue these (or other) changes, and to discover other things
that would need to be done before we could switch.

If we have that and the consensus is that it is important for linaro
then the Infrastructure team should be able to have these changes made
by the end of this cycle (assuming that the scope doesn't grow too much
during the discussions.)

Thanks,

James