> we don't control upstream and can't assign a > blueprint to a monthly milestone as we don't have control over when it > will actually land. How should this be handled?
Hmm, you've found... a loophole. :-) I need some time to reflect on this but off the cuff I can see three options: 1) Keep moving the BP or don't commit to a milestone until it's upstreamed. I don't like this option at all. 2) Once we send something upstream we can put the BP into "deployment" status and leave it on the milestone. Once upstream accepts the code then we could change it. I'm not sure I like this either. I feel like we're hiding the upstream work. 3) Once we send something upstream we put the BP into "implemented" status and move the upstreaming action somewhere else. (i.e. we don't block completion of a BP on upstreaming) This feels to me like a more natural fit for how we're organized but I don't have a solution for how to track upstreaming and ensure we are constantly looking at it (beyond patchwork that is). J _______________________________________________ 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
