{"issue":{"created_at":"2011-12-09T13:28:18Z","state":"open","updated_at":"2011-12-15T15:15:46Z","user":{"gravatar_id":"863e0a6594834fba2ec6cb9a4d9243ae","id":210896,"url":"https://api.github.com/users/alpacaaa","avatar_url":"https://secure.gravatar.com/avatar/863e0a6594834fba2ec6cb9a4d9243ae?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"alpacaaa"},"comments":3,"body":"I'm opening this issue to discuss and come up with a development workflow that will make \r\ndevelopers life easier and pushing changes to production as bulletproof as possible.\r\n\r\nThis is not meant to be specific to xpathr but hopefully be useful for future projects too.\r\n\r\nThe first thing I'd like to discuss is how to integrate changes into production.\r\nWe currently have an `ensemble` branch which should track the stable version of the app.\r\nGiven that, the production environment should always be synced with `ensemble`.\r\nThe `ensemble` branch tracks different submodules.\r\nIf a change is made to the repo the submodule is pointing to, the reference must be updated.\r\nThe problem is that if I make a change, I should update the submodule to point to my repo.\r\nBut then someone else integrates is work, so the submodule is updated again to track his repo.\r\nI fear this will soon lead to headaches.\r\n\r\nThe only solution I could find is to use one central repository as the source.\r\nEvery change must be first integrated with the central repository and then submodules are updated accordingly.\r\nThis is not very flexible, maybe there are better approaches.\r\n\r\nAnd then there's the database. We are currently using dump_db and which is nice and simple. Should we stick with it?","assignee":null,"id":2501443,"number":2,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"labels":[],"title":"Thoughts about how best collaborate on the project","html_url":"https://github.com/alpacaaa/xpathr/issues/2","closed_at":null,"milestone":null,"url":"https://api.github.com/repos/alpacaaa/xpathr/issues/2"},"action":"created","comment":{"created_at":"2011-12-15T15:15:46Z","updated_at":"2011-12-15T15:15:46Z","user":{"gravatar_id":"bac24b344b3f93a2a675c4c0ae6137d1","id":42321,"url":"https://api.github.com/users/bauhouse","avatar_url":"https://secure.gravatar.com/avatar/bac24b344b3f93a2a675c4c0ae6137d1?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"bauhouse"},"body":"Awesome! Thanks for fixing up the submodules.\r\n\r\nWe should also pull in the `ui` submodule as well. It is still pointing to my fork. We should probably just remove the Git repo for the UI and add the files into the `integration` branch. I suppose this should really become the `workspace` branch.","id":3162481,"url":"https://api.github.com/repos/alpacaaa/xpathr/issues/comments/3162481"}}