Skip to end of metadata
Go to start of metadata

Repository Structure

The primary repositories for CoprHD are hosted at review.coprhd.org. Anyone can clone the code from these repositories. Those who sign up as CoprHD Contributors will be able to create branches, push changes, and submit pull requests for approval by committers.

Mirrors of the CoprHD code have also been made available on GitHub for the convenience of GitHub users but code submissions & pull requests will not be accepted directly on GitHub.

 

Repository Listing

The following list describes the repositories which are currently a part of the CoprHD project.

Code Flow

The CoprHD project will follow a branching model for submitting code contributions to the project. After cloning the repository, a CoprHD Contributor should create a branch (from master or the appropriate release branch) in order to perform their development. Once the code is ready and tested, they can push the code back up to a corresponding branch on the CoprHD repository.

Once the code is present in Stash, the next step is to create a Pull Request for merge from the feature or bugfix branch into master (or the appropriate release-* branch).

At this point the code review process is initiated. Once that process is complete a CoprHD Comitter must merge the Pull Request into the target branch, thus completing the code submission.

More detail on the overall development process and standards can be found here:


Integrations - Openstack and Flocker


CoprHD is integrated with OpenStack and Flocker for which it will follow the below procedure for code commits


Integration with OpenStack


The contributors are required to make code commits on both the primary CoprHD repository as well as the secondary repository which is GitHub OpenStack repository. The procedure for CoprHD commits are in line with specifications as given above. There will be a separate code review process to be followed on GitHub OpenStack repository. It is binding on the contributor to maintain the code sync between the two repositories.



Integration with Flocker 


The contributors are required to make code commits on both the primary CoprHD repository as well as the secondary repository which is GitHub Flocker repository. The procedure for CoprHD commits are in line with specifications as given above. There will be a separate code review process to be followed on GitHub Flocker repository. It is binding on the contributor to maintain the code sync between the two repositories.






  • No labels