Lines Matching full:development

7 The rest of this section covers the scope of the kernel development process
12 influence the direction of kernel development.  Code contributed to the
15 :ref:`development_process` introduces the development process, the kernel
17 the patch development, review, and merging cycle are covered.  There is some
19 with kernel development are encouraged to track down and fix bugs as an
23 emphasis on involving the development community as soon as possible.
31 review. To be taken seriously by the development community, patches must be
38 of the development process; this section offers a number of tips on how to
46 for more information on kernel development.
60 (and companies) wishing to participate in its development.  Hardware
72 influence the direction of its development.  Proprietary products cannot
75 free software projects.  A typical three-month kernel development cycle can
79 Working with the kernel development community is not especially hard.  But,
85 surprising that Linux kernel development process differs greatly from
86 proprietary development methods.
88 The kernel's development process may come across as strange and
92 have a frustrating experience in store.  The development community, while
94 who will not listen or who do not care about the development process.
98 involved in reading it will be repaid in short order.  The development
127 relevant aspects of the kernel development process; most of these will be
164 - Participation in the development process is your way to influence the
165   direction of kernel development.  Users who complain from the sidelines
221 more development after its release.  This argument misses the value of
260 Questions about copyright-related issues are common on Linux development