One intention I have for the master branch is to keep it even with the latest release, and do current development off the develop branch.
When I saw issue #21 becoming more of a problem, I decided to merge develop into master, so anyone cloning the repo wouldn't experience the build problem.
After the next release, my goal will still be to go back to keeping the master even with the latest release.
One important note about using the current development code is that the default rmw data directory is hard-coded into rmw.h as $HOME/.config/testrmw, instead of $HOME/.config/rmw
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What I've been doing lately is merging develop into master immediately, unless I suspect some new development code needs more testing. Usually I only push changes that don't have any known serious issues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
One intention I have for the master branch is to keep it even with the latest release, and do current development off the develop branch.
When I saw issue #21 becoming more of a problem, I decided to merge develop into master, so anyone cloning the repo wouldn't experience the build problem.
After the next release, my goal will still be to go back to keeping the master even with the latest release.
One important note about using the current development code is that the default rmw data directory is hard-coded into rmw.h as $HOME/.config/testrmw, instead of $HOME/.config/rmw
This hasn't really gone according to plan.
What I've been doing lately is merging develop into master immediately, unless I suspect some new development code needs more testing. Usually I only push changes that don't have any known serious issues.