BTW, I've written up my understanding of the workflow at: https://wiki.linaro.org/MichaelHope/Sandbox/SummitWorkflow
Michael, this is great and if the Definition field for the blueprints gets updated at each stage, then it would be easy to track the progress of the blueprints ( at least the Definition part). Definition field states: New -> Discussion -> Drafting -> Review -> Pending Approval -> Approved Mounir On Wed, Oct 13, 2010 at 10:31 PM, Michael Hope <michael.h...@linaro.org>wrote: > Hi there. I'm confused about how we nominate and schedule things for > the upcoming summit. I've got a bunch of tr-* TR blueprints and a > related set of engineering blueprints. Some of these blueprints are > too big for one session and some need to be bundled up to fill up a > session. No matter what, summit blueprints need the > other-linaro-n-foo naming convention to work. > > What should I do? My best guess is create other-linaro-n-foo > blueprints for scheduling's sake and add the TR and engineering > blueprints as dependencies. > > BTW, I've written up my understanding of the workflow at: > https://wiki.linaro.org/MichaelHope/Sandbox/SummitWorkflow > > -- Michael > > _______________________________________________ > linaro-dev mailing list > linaro-dev@lists.linaro.org > http://lists.linaro.org/mailman/listinfo/linaro-dev >
_______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
