Currently, spicerack and cumin are both released by a single person, using custom personal tailored scripts.
It would be very beneficial if that task was able to be done by at least someone else, and better formalized and documented.
This task is meant to discuss and agree on how to achieve the above.
It's expected for the managers to agree/guide on how to share responsibilities.
Snippet of the irc chat that triggered this:
```
Spicerack roadmap doc: https://docs.google.com/document/d/10FIxIw5yTmFUdDC0M9ETTi5zDFWiqPJ2665sLJBoDTs/edit
121027 dcaro | volans: I would like to do a cumin + spicerack release, now that a bunch of the fixes and new functionality for wmcs toolforge/vps cookbooks is merged,
| What's the process?
121108 volans | dcaro: I can take care of the spicerack one, for the cumin one I need to get something else finished before releasing it
121139 dcaro | volans: can I help anyhow? would be nice to learn how to do it
121331 volans | I run a script, it's a bit tailored to my setup, it requires an account on pypi and also I'm signing all the releases with my gpg
121405 dcaro | my pypi account user is dcaro
121458 dcaro | my gpg key fingerprint is '718083A2AC8B314FB4CE11714071C7E1D26269C3'
121503 dcaro | ^ is that enough?
122057 volans | for what? the release script is totally experimental and tailored to my local env
122141 kormat | volans has made his own ball, and it only works at his home
122221 volans | it's more that I didn't had time to make it generic enough and uses a config file per repo that are not committd
122227 volans | because experimental
122304 volans | it also requires a script in the build host and one in the apt host to build the deb package and then reprepro it
122331 volans | but at least I use the same script for all the python packages I manage, because they share the same setup
...
122837 dcaro | volans: I'll add a note in the spicerack roadmap to add/generalize that script, ack?
123021 dcaro | I think it would be good if more than one person can release ;)
123344 volans | I agree in general, but is not just fixing the script. It's also a matter of who's responsabile for any follout of its deploy to production. What/how to
| test it when releasing it, coordinate with long-running cookbooks, etc.
123503 dcaro | that's ok, let's write that down
123732 dcaro | the only way of having more than one person being able to release, is well, sharing that responsibility and knowledge
123941 volans | yes and AFAIK SRE I/F is responsible for that area, but I'm not a manager
124132 dcaro | let's get one then :), I'll open a phab task to start a chat about it
```