strands_recovery_behaviours: 0.0.7-0 in 'hydro/distribution.yaml' [bloom]

Increasing version of package(s) in repository `strands_recovery_behaviours` to `0.0.7-0`:

- upstream repository: https://github.com/strands-project/strands_recovery_behaviours.git
- release repository: https://github.com/strands-project-releases/strands_recovery_behaviours.git
- distro file: `hydro/distribution.yaml`
- bloom version: `0.5.12`
- previous version for package: `0.0.6-0`

## backoff_behaviour

```
* Adjusting version number
* updated changelogs
* Backoff recovery fix.
* A simple behaviour for getting away from obstacles
* Contributors: Christian Dondrup, Marc Hanheide, Tom Krajnik
* Backoff recovery fix.
* A simple behaviour for getting away from obstacles
* Contributors: Tom Krajnik
```

## backtrack_behaviour

```
* updated changelogs
* Forgot to change the speed of going back to 0 as well
* Return success if backtrack moves at all
* Fixed bug
* Added output if no head camera
* Made the head turn the other way and not at all if no head_obstacle_cloud in sources
* Contributors: Marc Hanheide, Nils Bore
* Forgot to change the speed of going back to 0 as well
* Return success if backtrack moves at all
* Fixed bug
* Added output if no head camera
* Made the head turn the other way and not at all if no head_obstacle_cloud in sources
* Contributors: Nils Bore
* Forgot to change the speed of going back to 0 as well
* Return success if backtrack moves at all
* Fixed bug
* Added output if no head camera
* Made the head turn the other way and not at all if no head_obstacle_cloud in sources
* Contributors: Nils Bore
* Forgot to change the speed of going back to 0 as well
* Return success if backtrack moves at all
* Fixed bug
* Added output if no head camera
* Made the head turn the other way and not at all if no head_obstacle_cloud in sources
* Contributors: Nils Bore
* Forgot to change the speed of going back to 0 as well
* Return success if backtrack moves at all
* Fixed bug
* Added output if no head camera
* Made the head turn the other way and not at all if no head_obstacle_cloud in sources
* Contributors: Nils Bore
```

## strands_human_help

```
* updated changelogs
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* proper warning message
* stop waiting for mary as it might block the whole state machine
* Contributors: Bruno Lacerda, Marc Hanheide
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* proper warning message
* stop waiting for mary as it might block the whole state machine
* Contributors: Bruno Lacerda
```

## strands_monitored_nav_states

```
* updated changelogs
* changing default mongo loging back to true
* minor code clean
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* reducing time waited before clearing the costmaps
* making sure states preempt
* bug fix on clear costmaps recovery
* making sure bumper monitor does not try to restart motors after finding a barrier
* adding force clear costmap state;
  all nav recovery states put in the same file
* stop using max recover attempts for nav as it always output to topological nav anyway
* Contributors: Bruno Lacerda, Marc Hanheide
* changing default mongo loging back to true
* minor code clean
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* reducing time waited before clearing the costmaps
* making sure states preempt
* bug fix on clear costmaps recovery
* making sure bumper monitor does not try to restart motors after finding a barrier
* adding force clear costmap state;
  all nav recovery states put in the same file
* stop using max recover attempts for nav as it always output to topological nav anyway
* Contributors: Bruno Lacerda
* changing default mongo loging back to true
* minor code clean
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* reducing time waited before clearing the costmaps
* making sure states preempt
* bug fix on clear costmaps recovery
* making sure bumper monitor does not try to restart motors after finding a barrier
* adding force clear costmap state;
  all nav recovery states put in the same file
* stop using max recover attempts for nav as it always output to topological nav anyway
* Contributors: Bruno Lacerda
* changing default mongo loging back to true
* minor code clean
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* reducing time waited before clearing the costmaps
* making sure states preempt
* bug fix on clear costmaps recovery
* making sure bumper monitor does not try to restart motors after finding a barrier
* adding force clear costmap state;
  all nav recovery states put in the same file
* stop using max recover attempts for nav as it always output to topological nav anyway
* Contributors: Bruno Lacerda
* changing default mongo loging back to true
* minor code clean
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* reducing time waited before clearing the costmaps
* making sure states preempt
* bug fix on clear costmaps recovery
* making sure bumper monitor does not try to restart motors after finding a barrier
* adding force clear costmap state;
  all nav recovery states put in the same file
* stop using max recover attempts for nav as it always output to topological nav anyway
* Contributors: Bruno Lacerda
```

## strands_recovery_behaviours

```
* updated changelogs
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* Contributors: Bruno Lacerda, Marc Hanheide
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* Contributors: Bruno Lacerda
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* Contributors: Bruno Lacerda
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* Contributors: Bruno Lacerda
* magnetic strip monitor and recovery
  just asks to call a robot handler and puts a message on screen
  to restart the navigation there needss to be an explicit service call to /reset_barrier_stop done by one of us
* Contributors: Bruno Lacerda
```