7 Jun
2008
7 Jun
'08
4:20 p.m.
On Saturday 07 June 2008 10:24:42 am Colin Finck wrote:
Aleksey Bragin wrote:
This is managed (now) in Linux by having a "next release" branch where all
code that is ready to go into the next release is gathered, tested, etc...
Not that Linus doesn't still pick up patches for the mainline kernel - it
just helps resolve the merge problems between the trees.
DRH
--
Dialup is like pissing through a pipette. Slow and excruciatingly painful.
Ideally (as I explained in #reactos today to
blight_), I want the
trunk itself be directly committable only by a very limited
number of
persons, and all developers should be committing to "some other
place" at first, and then their patches merged by reviewers/testers
(yes, manually, sometimes just reviewing may be enough to commit/
reject the patch, sometimes a thorough testing must be involved,
maybe additional devs asked for a review).
blight_ called this as a "linux development model" with an
intermediate branch - yes, maybe, why not?.
The worst case I see with doing this using SVN is that we have a lot of
branches, which either depend on each other or are even incompatible to
each other.