series is definitely ok. We should try to standardize that on the James/Joey/Ilias thread for the picture and doc. In fact, let's just call it a recommended standard.
On Wed, Aug 17, 2011 at 8:21 AM, Ilias Biris <[email protected]> wrote: > On 16/08/11 23:45, Christian Robottom Reis wrote: >> On Mon, Aug 15, 2011 at 10:39:55AM -0400, James Westby wrote: >>> * More importantly nowhere in our process does a backlog currently >>> appear, so I don't see much value in doing this currently. The >>> slides presented by kiko mention a backlog, but don't explain how it >>> will be used, and I don't see a use for one in that presented plan. >> >> I wimped out on trying to solve the backlog problem together with this >> set of changes; sorry. I think the backlog can be handled by an explicit >> "backlog" milestone created for each project, and then rolled up into a >> project group milestone, and would be willing to help somebody >> interested in prototyping that along. > > > Backlog in a milestone or in a series? I quite like what Salveti is > doing in eg in https://blueprints.launchpad.net/linaro-ubuntu/backlog. > It means that one could even try to split a backlog in rough time ranges > such as quarters (so items for the quarter after the next one would be > still possible to place in the right time-basket and have them ready for > review at Connect). > > I am not sure if using a series there would be any LP limitation in the > rolling up you mentioned, but it would be great to have some rolling up > possible, otherwise I would have to dig into individual project backlogs > and that could be inconvenient. > > BR, > -- > Ilias Biris [email protected] > Project Manager, Linaro > M: +358504839608, IRC: ibiris Skype: ilias_biris > Linaro.org│ Open source software for ARM SoCs > _______________________________________________ Mailing list: https://launchpad.net/~linaro-project-management Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-project-management More help : https://help.launchpad.net/ListHelp
