Master branch awkward - Githubissues

stonier commented 11 years ago

Master branch doesnt really work as this repo is an automatic beast.

A jenkins scraper updates the package dependencies and version bumps quite regularly. That has to be done in the hydro branch since its scanning for hydro packages.

The problem with master is that it quickly becomes very old and may be missing official message packages in its dependency list

Workarounds

Dont worry about a master (a bit confusing).
An additional jenkins script could update this alongside hydro.
- How to do version numbers?
- A bit redundant?
The current jenkins scraper could just merge changes in hydro across whenever necessary.

stonier commented 11 years ago

I'm going to delete the master branch - whatever branches are here should reflect the curent state of the messages in whatever rosdistro we are scraping. In that sense, master is quite meaningless.

If there's no objections, I'll delete tomorrow.

stonier commented 11 years ago

Pointed the rosjava master rosinstaller to the hydro branch: https://github.com/rosjava/rosjava/commit/229c09c4ea9759577354c2a8a0f78d204f789988

stonier commented 11 years ago

Deleted master branch and left a note in the readme.

rosjava / rosjava_messages

Master branch awkward #4