+to pick the zip file of the distribution or controller can be executed
+right from there going into the distribution directory.
+
+Please note that this way no integration tests but only UT will be
+executed, if you are planning on committing code be aware that the
+code will be tested also for Integrations tests hence make sure before
+submitting a patch to build using the command:
+ "mvn clean install -Pintegrationtests"
+to get IT executed.
+
+HOW TO RELEASE ARTIFACTS
+========================
+Artifacts can be released in a bulk fashion or one by one depending on
+the need. Bulk release works well when in the need of establishing a
+baseline, for example on an upcoming major release. Single artifact
+release is useful for example for API bundles which are supposed to be
+used by others, this in fact seal the contract for that given version
+and others can rest assured won't change because the maven repository
+will not allow a the same artifact with the same version to be
+re-deployed.
+
+HOW TO BULK RELEASE ARTIFACTS
+-----------------------------
+Bulk release of the artifacts MUST be done only and exclusively by
+using the pom.xml present in the same directory of this
+README.OPENDAYLIGHT file. The pom.xml is just a pointer to the main
+distribution directory or in general to the one containing all the
+modules needs release.
+To perform the release from the top level just run:
+
+mvn -B release:prepare release:perform -Dgoals=deploy
+
+Well this is not supposed to be executed by a human but by an apposite
+Jenkins job because no committer or contributor has the necessary
+privileges to escape the code review process needed by the release
+process, but this is the logic behind.