Lines Matching full:development

3 How the development process works
6 Linux kernel development in the early 1990's was a pretty loose affair,
10 processes to keep development happening smoothly.  A solid understanding of
32 thus the leading edge of Linux kernel development; the kernel uses a
33 rolling development model which is continually integrating major changes.
36 merging of patches for each release.  At the beginning of each development
38 deemed to be sufficiently stable (and which is accepted by the development
40 new development cycle (and all of the major changes) will be merged during
62 best thing to do is to wait for the next development cycle.  (An occasional
73 As an example, here is how the 4.16 development cycle went (all dates in
88 How do the developers decide when to close the development cycle and create
110 next development kernel.  Kernels will typically receive stable updates for
111 a little more than one development cycle past their initial release.  So,
203    leave a poor impression in the development community.  Merging code
290 development cycle, approximately 5-10% of the patches going into the
309 Linux-next has become an integral part of the kernel development process;
323 them and track development.
346 As can be seen from the above text, the kernel development process depends
356 for kernel development, in that it performs quite well when dealing with
393 A great deal of Linux kernel development work is done by way of mailing
408 The core mailing list for kernel development is, of course, linux-kernel.
413 development community comes together as a whole; developers who avoid this
459 Getting started with Kernel development
462 Questions about how to get started with the kernel development process are
466 Companies often look to hire well-known developers to get a development
470 on Linux kernel development, given the investment of a bit of time.  Taking
480 noise which is distracting for the development community as a whole, so,
493 	persistence!) but that's fine - it's a part of kernel development.
501 building respect with the rest of the development community.