chore(workflow): updating branch reference from master to develop (#335)

* updating branch reference from master to develop in following files:
- CONTRIBUTING.md
- GOVERNANCE.md
- buildscripts/install-build-dep.sh
- code-standard.md
- developer-setup.md

* updating .circleci/config.yml

Signed-off-by: mayank <[email protected]>

.circleci/config.yml

@@ -1,13 +1,8 @@
-version: 2
-jobs:
-  build:
-    branches:
-      only:
-        - zfs-0.7-release
+version: 2.1
 jobs:
   build_tag_0:
     machine: 
-      enabled: true
+      image: ubuntu-1604:202104-01
     environment:
       - CODECOV_TOKEN=04a04811-63ec-4800-b1d6-f741dc7e079a
     working_directory: ~/github.com/openebs/zfs
@@ -58,7 +53,7 @@ jobs:
             bash <(curl -s https://codecov.io/bash)
   build_tag_1:
     machine: 
-      enabled: true
+      image: ubuntu-1604:202104-01
     working_directory: ~/github.com/openebs/zfs
     steps:
       - checkout
@@ -95,7 +90,13 @@ jobs:
             ztest
 workflows:
   version: 2
-  TAGS:
+  build_tag_0:
     jobs:
-      - build_tag_0
-      - build_tag_1
+      - build_tag_0:
+          filters:
+            branches:
+              only: zfs-0.7-release
+      - build_tag_1:
+          filters:
+            branches:
+              only: zfs-0.7-release

CONTRIBUTING.md

@@ -8,7 +8,7 @@ You can contribute to cstor by filling an issue at [openebs/cstor](https://githu
 
 * If you want to file an issue for bug or feature request, please see [Filing an issue](#filing-an-issue)
 * If you are a first-time contributor, please see [Steps to Contribute](#steps-to-contribute) and code standard(code-standard.md).
-* If you would like to work on something more involved, please connect with the OpenEBS Contributors. See [OpenEBS Community](https://github.com/openebs/openebs/tree/master/community)
+* If you would like to work on something more involved, please connect with the OpenEBS Contributors. See [OpenEBS Community](https://github.com/openebs/openebs/tree/HEAD/community)
 
 ## Filing an issue
 ### Before filing an issue
@@ -95,7 +95,7 @@ For setting up a development environment on your local machine, see the detailed
 ## Code Reviews
 All submissions, including submissions by project members, require review. We use GitHub pull requests for this purpose. Consult [GitHub Help](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-pull-requests) for more information on using pull requests.
 
-* If your PR is not getting reviewed or you need a specific person to review it, please reach out to the OpenEBS Contributors. See [OpenEBS Community](https://github.com/openebs/openebs/tree/master/community)
+* If your PR is not getting reviewed or you need a specific person to review it, please reach out to the OpenEBS Contributors. See [OpenEBS Community](https://github.com/openebs/openebs/tree/HEAD/community)
 
 * If PR is fixing any issues from [github-issues](github.com/openebs/cstor/issues) then you need to mention the issue number with a link in the PR description. like: _fixes https://github.com/openebs/cstor/issues/56_
 

GOVERNANCE.md

@@ -1,2 +1,2 @@
 This is a OpenEBS sub project and abides by the
-[OpenEBS Project Governance](https://github.com/openebs/openebs/blob/master/GOVERNANCE.md).
+[OpenEBS Project Governance](https://github.com/openebs/openebs/blob/HEAD/GOVERNANCE.md).

buildscripts/install-build-dep.sh

@@ -70,9 +70,9 @@ cd ..
 git clone https://github.com/${REPO_ORG}/libcstor.git
 cd libcstor || exit 1
 if [ "${BRANCH}" == "develop" ]; then
-  git checkout master
+  git checkout develop
 else
-  git checkout ${BRANCH} || git checkout master
+  git checkout ${BRANCH} || git checkout develop
 fi
 
 sh autogen.sh;

code-standard.md

@@ -2,7 +2,7 @@
 
 ## Sign your commits
 
-We use the Developer Certificate of Origin (DCO) as an additional safeguard for the OpenEBS projects. This is a well established and widely used mechanism to assure that contributors have confirmed their right to license their contribution under the project's license. Please read [dcofile](https://github.com/openebs/openebs/blob/master/contribute/developer-certificate-of-origin). If you can certify it, then just add a line to every git commit message:
+We use the Developer Certificate of Origin (DCO) as an additional safeguard for the OpenEBS projects. This is a well established and widely used mechanism to assure that contributors have confirmed their right to license their contribution under the project's license. Please read [dcofile](https://github.com/openebs/openebs/blob/HEAD/contribute/developer-certificate-of-origin). If you can certify it, then just add a line to every git commit message:
 
 ````
   Signed-off-by: Random J Developer <[email protected]>

developer-setup.md

@@ -25,7 +25,7 @@
   sudo make -j4
   sudo cp *.a /usr/lib
   ```
-* Make sure that you have installed libcstor in the system. Refer [installing libcstor](https://github.com/openebs/libcstor/blob/master/developer-setup.md)
+* Make sure that you have installed libcstor in the system. Refer [installing libcstor](https://github.com/openebs/libcstor/blob/HEAD/developer-setup.md)
 
 * Make sure that you have cloned and build fio(branch fio-3.7) code in the linux system.
   Please use below command for the fio
@@ -78,7 +78,7 @@ make
 ```
 
 * Test your changes
-Integration tests are written in c and c+. Test script is maintained at https://github.com/openebs/libcstor/blob/master/tests/cstor/script/test_uzfs.sh
+Integration tests are written in c and c+. Test script is maintained at https://github.com/openebs/libcstor/blob/HEAD/tests/cstor/script/test_uzfs.sh
 To run the run the integration tests.
 ```sh
 ../libcstor/tests/cstor/script/test_uzfs.sh -T all