A testing branch for testing specific things

[mhchia]

What is wrong?

Per @zscole 's suggestion, we should have a separate testing branch to push the testing specific materials

[mhchia]

@zscole @araskachoi we haven't done it previously. Will this still help if we introduce the testing branch now?

[zscole]

I think it would. It'll allow us to maintain better versioning control for a cleaner testing process. Whatever we want to test, we can just push to test branch without affecting anything else.

[mhchia]

@zscole no problem. I will just have a branch for that. Thank you!

[mhchia]

Added the branch testing . We can push all testing related logics to this branch, and merge the code in master we want anytime.

[mhchia]

@zscole @araskachoi

Since we already have the branch testing. We are thinking if the following strategy makes sense: We

• push all testing related logics to the branch testing, and we can separate the testing data into directories, according to the versions or commits in the branch master
• push code changes to the branch master
• merge the master branch to the branch testing whenever we want to change the code base for the testing
• [possibly, this is just my personal thoughts] release some version in another branch release, and if we want to test against a specific version, just merge the commit of that version to the branch testing

Thoughts?