Lines Matching full:development

9 The rest of this section covers the scope of the kernel development process
14 influence the direction of kernel development.  Code contributed to the
17 :ref:`development_process` introduces the development process, the kernel
19 the patch development, review, and merging cycle are covered.  There is some
21 with kernel development are encouraged to track down and fix bugs as an
25 emphasis on involving the development community as soon as possible.
33 review. To be taken seriously by the development community, patches must be
40 of the development process; this section offers a number of tips on how to
48 for more information on kernel development.
62 (and companies) wishing to participate in its development.  Hardware
74 influence the direction of its development.  Proprietary products cannot
77 free software projects.  A typical three-month kernel development cycle can
81 Working with the kernel development community is not especially hard.  But,
87 surprising that Linux kernel development process differs greatly from
88 proprietary development methods.
90 The kernel's development process may come across as strange and
94 have a frustrating experience in store.  The development community, while
96 who will not listen or who do not care about the development process.
100 involved in reading it will be repaid in short order.  The development
129 relevant aspects of the kernel development process; most of these will be
166 - Participation in the development process is your way to influence the
167   direction of kernel development.  Users who complain from the sidelines
223 more development after its release.  This argument misses the value of
262 Questions about copyright-related issues are common on Linux development