On Tue, Aug 23, 2011 at 10:48 AM, Paul Larson <[email protected]>wrote:
> What about this: > Split the blueprint into an implementation blueprint, and an upstreaming > blueprint (if needed) that are dependencies of a tracking blueprint for the > thing you are trying to implement and move upstream (more could be added if > further dependencies are needed, and warrant having a blueprint to track the > tasks for them). This way you could estimate the pieces one chunk at a > time, and take your best guess on when to target the tracking blueprint for > the whole thing. > > example > 2011.09: > Change foo to bar: Implementation > 2011.10 > Change foo to bar: upstreaming > Change foo to bar > > If upstreaming looks like it will take longer than originally anticipated, > you just push the upstreaming blueprint, and the tracking blueprint to the > next month. The overall blueprint (Change foo to bar) doesn't get marked > complete until all its dependencies are done. > This is a good way to think about it. The issue when a bp's get stuck in upstream, we don't know whether it will be done next month or the month after, we don't want to keep pushing the upstreaming bp to next month and the next ... > > -Paul Larson > -- Mounir Bsaibes Project Manager Follow Linaro.org: facebook.com/pages/Linaro/155974581091106 http://twitter.com/#!/linaroorg http://www.linaro.org/linaro-blog <http://www.linaro.org/linaro-blog>
_______________________________________________ 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
