-----Original Message----- From: ros-dev-bounces@reactos.com [mailto:ros-dev-bounces@reactos.com] On Behalf Of Alex Ionescu Sent: 9. marts 2005 22:17 To: ReactOS Development List Subject: Re: [ros-dev] Registry and ObjectManager (was FreeLdr Part II)
<snip>Talk about all the work that went into the branch</snip>
I'll try to be more clear since you seem to be confused about my points. I'm NOT arguing that the product is bad. I haven't looked at the branch yet, but I'm sure a lot of great work went into it. ReactOS is still a volunteer effort and everyone can (and should) be able to decide for him/herself what they want to contribute. This is a great motivation factor, but it's also a disadvantage so we should make sure that our processes minimize the damages that can happen from that.
What I AM arguing for is that THE PROCESS could be better. Traditionally there are two types of branches.
1) Release branch. Usually created some time before a release to have a more stable product at the time of a release. Only bugfixes go to this branch.
2) Feature branch. Usually created to achieve a well-defined purpose (e.g. the implementation of a new feature). Only changes required to achieve the well-defined purpose are committed to this branch.
Alex_devel_branch is a combination of the two and it has some disadvantages.
* Bugs that that could have been fixed on trunk are annoying to trunk developers. The bugfixes that go only to the branch are not in trunk (until merged there from the branch) where most developers work and is thus annoying to these developers.
* Risk of duplicating work. We'll have more branches to track bugfixes on so it's harder to know which bugs has been fixed and which hasn't.
Casper