From: Ylinen, Mikko [mailto:[email protected]] Sent: Tuesday, June 24, 2014 2:39 AM To: Schaufler, Casey Cc: [email protected] Subject: Re: [Dev] How to handle divergence in profiles.
Hi Casey, On Fri, Jun 20, 2014 at 1:38 AM, Schaufler, Casey <[email protected]<mailto:[email protected]>> wrote: I want to make a change to fix a problem in Tizen-ivi. The change is in the platform/upstream/filesystem package. The tizen branch is obviously not the branch used to create the ivi images. There are 7 branches with "ivi" in the name. Which should I be working from, and how would I know which to work from? 'tizen' is being used for all Tizen 3.0 development, including Tizen IVI. However, what's in IVI might be pointing to an older commit in that branch. So how can I fix a bug reported against IVI when IVI is six months out of date? Tizen Common follows the bleeding edge versions of each Git (usually HEAD) because Common is doing the pre-integration for must stuff. Profiles (e.g. IVI) will sync later once Common is verified the basic stability and announced daily/weekly releases. I've written this wiki that explains how IVI follows Common pre-integration and how submissions are done: https://wiki.tizen.org/wiki/IVI/Tizen_IVI_OBS_Reboot I look at the package in question and see that what’s in IVI is very different from what’s in Common. There is, it turns out, a *different* problem in Common. I can fix Common, but that does nothing for IVI. I keep getting pestered to fix IVI, but until it catches up there’s nothing I can do. Further, other “unrelated” changes impact the solution. How can I find the state of IVI without dredging the build logs? The tree does not tell me. (The process was slightly different for IVI previously, thus the name 'reboot'). -- Mikko
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
