Move development to a separated branch.

[vldmrkl]

After we set up the project (Initialized create-react-app, added Travis CI, Readme.md, Contributing.md, I think we should move the main part of development from 'master' branch to develop branch.

So the idea is that we are going to push smaller changes into develop, and master is the branch where the source code of HEAD always reflects a production-ready state (read https://nvie.com/posts/a-successful-git-branching-model/ for inspiration).

It should increase maintainability of the project.

[seanprashad]

Sorry for not getting around to this sooner @klymenkoo - I haven't discussed this as yet with Mera, but here are my brief thoughts until she can join us:

• I've seen this method of branching before and it has worked out quite well! I am open to the idea of having something like master (which will eventually be deployed to Heroku) and develop (where PR's will be opened against, also available on a dev version of Heroku for us to play around with)

• With that being said, I don't have a problem with maintaining the current flow of work from contributorsName/issue-X into master - I'm a big believer in "If it's not broken, don't fix it" but let's hear what others have to say

Are there any other OSS projects that use this method of branching? I'd be interested in talking to those maintainers to get a better understanding if this is something we want to pursue!