Jump to content
  • 0
Sign in to follow this  
Kashiro

Asking about svn

Question

3 answers to this question

Recommended Posts

  • 0

Trunk is the main branch where all fixes and new code goes. The other branches are mainly developmental and it's where our developers test their code so in case there's some unstable code it will be fixed right there on the branch before getting committed to trunk.

 

In practice, the branches are rarely used but the code that's committed to trunk is mostly right most if the time.

Share this post


Link to post
Share on other sites
  • 0

correct me if im wrong

 

so before applying to the main branch ( trunk ) it will have the branches first? such as fixes etc

 

another question

 

so why need so many branch why is not just 1 branch? before applying to main trunk?

 

is there any difference with implementing script codes etc in branches than the trunk?

 

thanks for the answers i just want to enlighten :D

Share this post


Link to post
Share on other sites
  • 0

Most developers in Hercules just commit to trunk directly without testing the code on a developmental branch, but they try and test the code themselves to avoid major bugs.

 

As for the branches, when a big feature is planned to be added or for some other reasons, one or more developers may decide to branch trunk and work on it on that branch. That way, it's like they have a own repository that can be worked on as if it was the main one. Branches can be of multiple nature (changing script engine to LUA, password encryption improvements, etc) and that's why there isn't only one branch.

 

Think of the development of Hercules like a tree in reverse: some code is directly in the trunk and the branches start somewhere out of it and end up contributing to that trunk.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.