Hi Joey, The idea (for now, at least) is just to track patches submitted (and accepted) upstream. It's currently not integrated with any of the other tools we use.
Ideally the engineers would only have to CC their patches to [email protected] and we'd watch the upstream branches and detect which ones have been accepted. In practice it doesn't work like that, though, because sometimes patches are changed upstream before being committed and we don't have a reliable way to detect superseded patches, so we have to ask the engineers to regularly check their list of patches with no feedback and update their state when appropriate. That should be everything the engineers have to do, though. Cheers, On Thu, 2011-06-16 at 09:28 -0600, Joey Stanford wrote: > Hi James & Salgado, > > The PMs got together today and are a little lost on the process > surrounding patchwork. > > Is there any specific process surrounding responses from upstream? > e.g. break the patch into multiple patches? how does WI status change > based upon reply? etc./ > > Can you say a few words on this? > > Joey -- Guilherme Salgado <https://launchpad.net/~salgado>
signature.asc
Description: This is a digitally signed message part
_______________________________________________ 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
