5th October 2009
|
|
More noise than signal
|
|
Join Date: May 2008
Location: USA
Posts: 7,983
|
|
This is -my- understanding. It's probably wrong, therefore.
- Every patch, no matter how trivial, requires peer review.
- Developer and peers are listed in each patch log.
- Functional patches must be tested before commitment. Therefore, each developer keeps their own working set containing their uncommitted patches that are not yet ready for committment.
- Snapshots are built, when needed, as needed. These vary. Obviously, snapshots are made on all architectures for -beta, and for flag days and other architectural changes... but there are usually many more snapshots created during the normal development cycle.
- As BSDfan666 said, snapshots may include uncommitted patches. If you run -current by upgrading snapshot to snapshot, and many people do, you may occasionally be running uncommitted code. If you run -current by installing a snapshot, then building from source, you will be running only committed code.
- Huge, complex hunks of code may be developed in its own CVS branch, by the developer(s) working on it, prior to being synced into the main branch. Historical examples: multiprocessing, and the Unified Buffer Cache. X11 has been historically kept in separate branches: XF3, XF4, and XENOCARA
Last edited by jggimi; 5th October 2009 at 05:20 PM.
|