-For Arno release the jobs will be run once per day per installer (Fuel and Foreman) on stable/arno branch.
-Since this is in addition to the jobs for master branch and jobs have long run time,
-this might need re-evaluation as we go on.
-
-The artifacts arno/stable jobs produced are stored in the new directoies on artifacts.opnfv.org.
-
-The artifacts produced by daily jobs would be stored
- For stable/arno, the storage locations will be <project_name>/arno/<artifact_name>.iso
-The docs produced by daily and merge jobs would be stored
- For stable/arno, the storage locations will be <project_name>/arno/docs/<document_name>
-
-No changes in overall functionality in merge and verify jobs: they will continue doing builds only ::
-
- genesis-fuel-verify-master, genesis-fuel-verify-stable-arno,
- genesis-fuel-merge-master, genesis-fuel-merge-stable-arno,
- genesis-foreman-verify-master, genesis-foreman-verify-stable-arno,
- genesis-foreman-merge-master, genesis-foreman-merge-stable-arno
-
-
-Team organization
------------------
-
-Project specific tasks
-~~~~~~~~~~~~~~~~~~~~~~
-
-Each of the 5 projects that contributed to Arno will dedicate some committers
-which would be in charge of reviewing backports for their project, following the stable branch policy.
-It is in the responsibility of each project how to select those committers (e.g. vote in the team).
-
-The group of these committers here are sometimes called the
-"stable branch maintenance team" or "stable-mtc" without this being necessarily a team with own organization.
-
-Stable branch management
-~~~~~~~~~~~~~~~~~~~~~~~~