Define a git workflow to integrate new features.

[SimonKrafft]

We have to determine, how we want to collaborate in the future and how we separate production code from development code.

I would propose git-flow as a branching strategy, which adds a long-running "develop" branch to the "main" branch. New features or testing phases are third-level branches that shadow the "develop" branch.

from: https://www.youtube.com/watch?v=Uszj_k0DGsg

[mehran-hosseinzadeh]

define a develop branch and pull that by all

[SimonKrafft]

As discussed in today's meeting, we will stick to GitFlow as our branching strategy. Therefore, I added a 'develop' branch to the MedicalAnnotationFramework and the media_viewing_widget repo.
@FreshP-min and @mehran-hosseinzadeh, please pull the most recent commits from the develop branch before you start implementing new features and fixing bugs.
@Valaybundele you can now push your latest changes on #39 and #40 into the develop branch, but remember to update your git remote with 'git remote set-url origin [email protected]:cgtuebingen/MedicalAnnotationFramework.git' and pull before you push.