Post-Acceptance Checklist for Orchard Administrators

After you have deemed a new set of autopkg recipes meet our guidelines and perform as they should, do the following:

1. Merge the pull request into the master branch of the relevant repository using the green button on Github, which closes the pull request.

2. On the build host, do a sudo -u autopkg git pull in the relevant repository's local directory (i.e. /srv/autopkg/Recipes, /srv/autopkg/RecipeOverrides etc)

3. If this is in the orchard-recipes repo, please also do a sudo -u autopkg git push autopkg master to update the version in the main autopkg repo. This does not need to be done for overrides, or private recipes.

4. Upload a 350x350 (or higher) png file of the icon, named the same as the munki pkginfo's Name key to /srv/munki/orchard_repo/icons on the build host.

5. Run sudo -u autopkg autopkg run RecipeName.munki to run the recipe and import its output into Munki on the build host.

6. If this runs without problems, wait for the next munki-staging run (00 and 30 minutes past the hour) to complete and then move the resultant pkg to 'To Stable' on Trello (the first version of a pkg is always considered stable, future versions should be staging into testing if the recipe is correct)

7. Now add the munki recipe/override to the autobuild - create a symbolic as the autopkg user, link to it in the /srv/autopkg/BuildRecipes folder on the build host.

8. Finally create the entry for the software in the relevant section(s) in the manifest(s) /srv/munki/orchard_repo/manifests on the build host].

9. Inform the author of the recipes that the software is now available in the Orchard Software Centre and to test.