On Tue, 19 May 2015 12:49:51 +0200 Tomasz Swierczek <[email protected]> said:
> Apart from being a common part of all profiles, this *really is* the base for > work of Tizen security team. > > Without Common we will have a big problem in keeping all our work properly > tested & released - and we may quickly end up with 3 separate "Tizen's" on > each profile. > > > Like Stephane wrote, Common's status *needs to be clarified*. Unfortunately, > I'm not the person with authority to do this. the status is the same. the problem is - people don't really care. they are tasked to work on tizen tv or tizen mobile, so that's what they work on. everything else is irrelevant. they are not interested in common or any other profile. it's the reality. our core problem is that we HAVE PROFILES (as in separate tizen stacks). this should cease imho. there should be just "tizen". a tizen MOBILE device may add/include some extra daemons or packages (or remove some). same for tv or ivi etc. etc. - a profile should be nothing more than a list of guaranteed minimum libraries, services and "ui style". > Tomasz Świerczek > Samsung R&D Institute Poland > Samsung Electronics > Office +48 22 377 95 59 > Cell +48 503 135 021 > [email protected] > > > -----Original Message----- > From: Dev [mailto:[email protected]] On Behalf Of Stéphane Desneux > Sent: Tuesday, May 19, 2015 11:01 AM > To: [email protected] > Subject: [Dev] Misalignment of Tizen profiles on Tizen:Common > > Dear all, > > As you may know, Tizen profiles should be aligned on Tizen:Common regularly > (see tizen wiki: https://wiki.tizen.org/wiki/Common) > > In particular, this has the following consequences: > - packages in Common should be newer or identical to packages in profiles > - except profile-specific packages (most with git path profile/<$profile>/*), > all packages should be submitted to Tizen:Common. If the submission is > accepted, then the packages would land on a specific profile after a > synchronization step (roughly, a group submission with the delta) > > This process was used for IVI last year to allow the IVI team to focus only > on IVI specific packages (~80 packages) and let T:Common gather the shared > work on the rest of the distro (~850 packages). The benefits when developing > multiple profiles is obvious... > > But since the beginning of the year, we observe a growing number of > submissions going directly on profiles (TV, Mobile, Wearable), completely > bypassing T:Common to speed up integration, mostly on Tizen:TV: some > maintainers submit changes using explicit branches 'tizen_tv', 'tizen_mobile' > and 'tizen_wearable' to bypass T:Common and avoid the Common->TV > synchronization step. > > This has *huge* consequences: > * profiles are not synchronized anymore with Common nor with other profiles > * Common can't be used anymore as an integration, factoring point used for > validating new patches and the work has to be done multiple times (once per > profile) > * less visible and even more evil is the chain reaction it triggers: as some > APIs have changed in profiles but not in T:Common, some other packages > submitted correctly don't build anymore on T:Common and must be rejected to > keep a correct build. > * people are still working on Tizen:Common to fix bugs and integrate new > functionnalities. Without a proper synchronization on Common, those > improvements won't land in profiles. > > To get the details, we made a small script that analyzes the differences > between two or more profiles, based on manifests in snapshots. It's quick and > handy: https://wiki.tizen.org/wiki/Profile_alignment_on_Tizen:Common > > You can find attached to this email the result when comparing the recent > snapshots of Common, TV, Mobile and Wearable: we have currently 88 conflicts > to solve (~10% of T:Common) and it's growing every day. > > Tizen:Common status must be clarified and guidelines to maintainers should be > updated ASAP, before the gap to synchronize has become too big. > > Best regards > -- > Stéphane Desneux > Intel OTC - Vannes/FR > gpg:1CA35726/DFA9B0232EF80493AF2891FA24E3A2841CA35726 > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev -- Carsten Haitzler (The Rasterman) <[email protected]> _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
