Le 04/12/2014 15:26, Chanho Park a écrit : > Hi, > > As I know, we agreed we'll use LTS or LTSi version for the tizen reference > kernel version[1]. Please note we can use not only LTSi but LTS kernel. > We'll use LTS kernel in mobile profile. Chanho,
remember that the discussion that I had was about Tizen Common. Each profile has its own freedom. As we speak today, LTSI has not yet released any kernel (we expect the first one to come out in 1 or 2 weeks). Until that time Common is aligned on LTS. > > BTW, to merge memfd and kdbus feature, should we wait until next merge > windows of LTSi? To get in Common yes, but in a profile kernel you can do it today if you have the agreement of the maintainer/architect for that profile. > I think it's really slow development process. I think LTSi kernel will be > good we've done the development. > During we develop the platform, we would better to accept a new feature > after we examine it thoroughly. Full freedom is provided to each platform. But then they are on their own. > > If it is impossible to accept the new feature on the stable kernel until > we've got any review from LTSi, how do we consider landing experimental > kernel for the new feature? > > [1] https://wiki.tizen.org/wiki/Standard_of_Tizen_Reference_Kernel_Version We are updating the Wiki to clarify the issue. In short : Admission condition. Your patch has been accepted in one Linux stable kernel. 1) Gold ticket to get a guaranteed acceptance in next Common-Stable. Get your patch accepted in LTSI. Nothing else to do, Stéphane will darg it to Common-Stable. 2) Silver ticket get your code accepted by LTSI maintainer and explain to the community why we should go through the pain of pre-accepting the patch in Common-Stable before than LTSI makes a release. Then we will integrate it and monitor which LTSI release will provide it (in order to remove the patch when not needed any more). 3) Bad ticket. Your code has been reviewed by LTSI. They like it but cannot integrate it for a good raison (other than being a bad patch/dangerous patch) Multiple profiles need/want the feature and have explain their motivation to the community. Then we will integrate it in Common-Stable and maintain it. > -- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
