alpacaaa/xpathr — Issue #2: Thoughts about how best collaborate on the project
Author: alpacaaa
Created: 2011-12-09 13:28:18+00:00
State: open

I'm opening this issue to discuss and come up with a development workflow that will make
developers life easier and pushing changes to production as bulletproof as possible.

This is not meant to be specific to xpathr but hopefully be useful for future projects too.

The first thing I'd like to discuss is how to integrate changes into production.
We currently have an `ensemble` branch which should track the stable version of the app.
Given that, the production environment should always be synced with `ensemble`.
The `ensemble` branch tracks different submodules.
If a change is made to the repo the submodule is pointing to, the reference must be updated.
The problem is that if I make a change, I should update the submodule to point to my repo.
But then someone else integrates is work, so the submodule is updated again to track his repo.
I fear this will soon lead to headaches.

The only solution I could find is to use one central repository as the source.
Every change must be first integrated with the central repository and then submodules are updated accordingly.
This is not very flexible, maybe there are better approaches.

And then there's the database. We are currently using dump_db and which is nice and simple. Should we stick with it?