Continuous integration-the development process for a small team of PHP projects.

Want to consult under the small team under 3-4 people, if the project version of the development Process control. Development---submit version->beta->, if effective control. There is no better development process in addition to SVN version control, what open source software is available?

Is there a set of effective PHP continuous integration development processes?

Reply content:

Want to consult under the small team under 3-4 people, if the project version of the development Process control. Development---submit version->beta->, if effective control. There is no better development process in addition to SVN version control, what open source software is available?

Is there a set of effective PHP continuous integration development processes?

Common open source software is as follows:

• Product, project management, bug tracking Zentao
• Document DokuWiki Apigen Phpdocument
• Version Control SVN
• Unit Test PHPUnit SimpleTest
• Deployment and continuous Integration phing Xinc
• IDE NetBeans ECLIPSE+PDT

Development process, only in the case of research and development level, the simple is product-centric, product manager, development team, testing team three roles to complete.

1. Product Manager to create products and requirements;
2. The project manager creates the project, determines the project needs to be done, decomposes the task, assigns to the person;
3. Testers test, submit bugs.

Small team three or four people in the case, usually each person to have a variety of roles, life, such as play, all by acting, grasp the positioning of each role, product manager is the protagonist, the value of the actor will look at the final product performance.

In the specific coding phase, it is recommended to use the PHP framework to write complete documentation comments.

Checkin is not allowed on the online environment, only checkout allowed
Test environment each development own a development directory, Apache configuration VirtualHost , each with a different domain name test

For 3 to 4 people, SVN is sufficient ... How low the threshold is ... The most is to make a change before shouting: I want to change a file, who also change the words to pay attention to the merge later.

College students ' opinions, low gold content. According to my classmates and my cooperation experience to say, for reference only.

Stealing that the biggest advantage of a small team is flexibility, everyone can maximize their ability, in the way of working to try to avoid unnecessary regulations. (All people are reliable premise, don't say on the three or four people also have not reliable soy sauce ... ）

If you press the previous sentence, versioning is a must, otherwise everyone you punch my foot even if only three or four people will be confused, git or svn or anything else casually choose, because my home no network, has been using Git.

As for what version or what, I have not touched, my own way is to find out the project plan must have, can have and can not have three types of functions. And then solve in turn, basically the third kind of function can not end up "no".

