Merge pull request #175 from muffinresearch/add-deps-docs-push-duty

Add docs re: project dependencies

docs/server/push-duty.rst

@@ -16,15 +16,33 @@ Check out the `Add-ons calendar <https://calendar.google.com/calendar/embed?src=
 Before the push
 ---------------
 
-Tag the repos
-+++++++++++++
 
 The code that will go in production on Thursday is tagged on Tuesday. The
 following repositories are tagged:
 
     * `addons-server <https://github.com/mozilla/addons-server/>`_
     * `addons-frontend <https://github.com/mozilla/addons-frontend/>`_
 
+Project Dependencies
+++++++++++++++++++++
+
+Project dependencies are not tagged as part of the push duty responsibilities.
+If you're working on a feature in a project that's a dependency of a project
+e.g. ``addons-linter``, then it's *your* responsibility to make a release and
+update the project that consumes that dependency in time for the tag.
+
+This way we can ensure that:
+
+  * Dependency packages are built and released in time for the tag.
+  * The new feature in the new version of a package has been validated on
+    -dev.
+
+Making multiple releases of a package during a weekly milestone is totally
+fine since this helps with testing smaller sets of changes.
+
+Tag the repos
++++++++++++++
+
 Tags are of the format: ``YYYY.MM.DD``,
 
 .. note:: The date is the date of the push, not the date of tagging.