I reverted the multi-projects commit for now, as it wreaked havoc. It causes the ubuntu database to only contain the linaro milestones, and thus breaking all the milestone charts and sending tons of errors to everyone.
What is the rationale here in the first place? linaro has separate projects in Launchpad, thus we should also have separate WI reports/burndowns, such as
(you also use a different burndown chart style). Trying to merge different projects with different milestones into one set of charts will just create confusion. Either you need to ignore the milestones from either side (which is obvioulsy not acceptable), or you need to merge the milestones from all projects. But this will create a combinatorial explosion of charts, and also break the automatic reset of per-milestone burndown charts, so it's also not feasible.
I reverted the multi-projects commit for now, as it wreaked havoc. It causes the ubuntu database to only contain the linaro milestones, and thus breaking all the milestone charts and sending tons of errors to everyone.
What is the rationale here in the first place? linaro has separate projects in Launchpad, thus we should also have separate WI reports/burndowns, such as
http:// people. canonical. com/~platform/ workitems/ linaro- pm-wg/all. html people. canonical. com/~platform/ workitems/ linaro- toolchain- wg/all. html
http://
(you also use a different burndown chart style). Trying to merge different projects with different milestones into one set of charts will just create confusion. Either you need to ignore the milestones from either side (which is obvioulsy not acceptable), or you need to merge the milestones from all projects. But this will create a combinatorial explosion of charts, and also break the automatic reset of per-milestone burndown charts, so it's also not feasible.
So let's discuss that a bit further first.