# Releases and Known Issues

## Known Issues

The following items are current EasyCLA v2 behavior notes and known limitations:

* [Auto-Branch Protection behavior](#auto-branch-protection)
* [Organization Association](#organization-association)

### Auto-Branch Protection

Auto-Branch Protection behavior currently differs by provider:

* **GitHub:** when EasyCLA auto branch protection is enabled, EasyCLA configures branch protection rules that target all branches.
* **GitLab:** EasyCLA currently protects only the project's default branch automatically. If non-default branches also require EasyCLA enforcement, configure those branches manually in GitLab.

### Organization Association

Currently, user roles in EasyCLA can only be associated with a single company or organization at a time.

## Releases

Release notes for the EasyCLA backend and APIs can be found at <https://github.com/linuxfoundation/easycla/releases>.

Release notes for the EasyCLA Contributor Console can be found at <https://github.com/linuxfoundation/easycla-contributor-console/releases>

EasyCLA V2.0 supports projects with a parent-child model of any number of hierarchy levels without any limit in the depth of the hierarchy. The following is an example:

* Parent Project
  * Child Project
    * Grand Child Project
      * Great Grand Child Project

        * Great-Great Grand Child Project

        ….