Remove Berksfile.lock from dev branches

blueprint remove-berksfile-lock-from-dev-branches

Change-Id: I9b9e4661c444d9d838639be3132365f4f0d1cb50

.gitignore

@@ -1,3 +1,4 @@
 .bundle/
 .cookbooks/
 .project
+Berksfile.lock

Berksfile.lock

@@ -1,36 +0,0 @@
-{
-  "sources": {
-    "openstack-identity": {
-      "path": "."
-    },
-    "openstack-common": {
-      "locked_version": "8.0.0",
-      "git": "git://github.com/stackforge/cookbook-openstack-common.git",
-      "ref": "bf7f7bc3f2f8a1db112afd790aa54998a6cde40f"
-    },
-    "apt": {
-      "locked_version": "2.3.0"
-    },
-    "database": {
-      "locked_version": "1.4.0"
-    },
-    "mysql": {
-      "locked_version": "3.0.0"
-    },
-    "openssl": {
-      "locked_version": "1.1.0"
-    },
-    "build-essential": {
-      "locked_version": "1.4.2"
-    },
-    "postgresql": {
-      "locked_version": "3.3.4"
-    },
-    "aws": {
-      "locked_version": "1.0.0"
-    },
-    "xfs": {
-      "locked_version": "1.1.0"
-    }
-  }
-}

README.md

@@ -250,6 +250,16 @@ Testing
 
 Please refer to the [TESTING.md](TESTING.md) for instructions for testing the cookbook.
 
+Berkshelf
+=====
+
+Berks will resolve version requirements and dependencies on first run and
+store these in Berksfile.lock. If new cookbooks become available you can run
+`berks update` to update the references in Berksfile.lock. Berksfile.lock will
+be included in stable branches to provide a known good set of dependencies.
+Berksfile.lock will not be included in development branches to encourage
+development against the latest cookbooks.
+
 License and Author
 ==================