Lines Matching refs:team

13 development cycle, the Yocto Project team chooses a Linux kernel based
20 team knows that the ``kernel.org`` final release will clearly be within
23 This balance allows the Yocto Project team to deliver the most
25 team has a stable official release for the baseline Linux kernel
95 Once a Yocto Linux kernel is officially released, the Yocto Project team
104 During the uprev cycle, the Yocto Project team uses an ongoing analysis
107 subsequent Yocto Linux kernel development. The team continually monitors
109 interest. The team does consider back-porting large features if they
117 team's Yocto Linux kernel development strategy. It is the Yocto Project
118 team's policy to not back-port minor features to the released Yocto
150 implemented by the Yocto Project team using the Source Code Manager
171 Using Git's tagging and branching features, the Yocto Project team
186 same feature twice internally in the tree. Rather, the kernel team
192    The Yocto Project team strives to place features in the tree such
195    are merged, the team cannot always follow this practice. In those
196    cases, the team uses isolated branches to merge features.
200 kernel types. So, for these types, the team creates branches off the end
205 So again, rather than store the BSP twice, the team only stores the
272 Yocto Project kernel development team.