[ros-dev] ReactOS Development Process

Aleksey Bragin aleksey at reactos.org
Wed Oct 3 10:50:06 CEST 2007


	Hello,
recently, different people raised a question: How should development  
process evolve with time, when ReactOS has more (much more)  
developers willing to contribute code?

There are many possibilities, however all of them assume more or less  
an overhead, and need additional human resources.
I will outline one suggested method, and want you (developers) to  
"constructively criticize it", improve it, or offer a better method.  
Even if it involves changing current version control system, or  
anything - suggest the method.

So, the suggestion I've already got is this:
Trunk is writable only by a so-called Integrator person (maybe a few  
persons). Branches are writable by a big amount of developers.
Typical development process is as follows:
1. A developer creates a ticket in issue-tracking system (currently  
Bugzilla), where he describes what's wrong and what his change fixes/ 
improves.
2. He creates a branch with a name BZ-XYZ (where XYZ is ticket's  
number), and commits his changes there.
3. An integrator, daily, goes through all BZ-... branches, does svn  
merge to trunk of each branch, test it, if no regression occurs, he  
commits changes to trunk and svn deletes the respective BZ-... branch.


Some kind of integration system is definitely needed, so please avoid  
fast answers like "Let's stay as we do now". Better approach is  
needed, and I'm looking for it. If you can offer something - do so.



With the best regards,
Aleksey Bragin.


More information about the Ros-dev mailing list