3 ms·
I think a lot of this debate argues for the sysadmin role being part of the dev team. The only real way to get both constraints (production stability and updat
by warbiscuit 10y ago
I think a lot of this debate argues for the sysadmin role being part of the dev team. The only real way to get both constraints (production stability and update to date fixes/features) is to have fast feedback between the interest holders of two sides.
In the python-specific case -- the requirements.in / .txt files for the virtualenv should be part of the software VCS, but the sysadmin should be able to edit & pin things just like the devs, so that they can bring their expertise to the container, rather than having to fight it.
---
Mind you, my opinion might not scale - I'm part of a small enough team that I'm holding both those roles, but I try make sure to spent time wearing both "hats", so that one role doesn't get more man-hours clocked.
- crdoconnor 10y agoIMO if a sysadmin wants to have visibility into the requirements.txt that's fine. If they want to enforce a policy of pinning versions, that's very welcome (though I would do that anyway). If they have specific, relevant comments about upgrades of specific packages - again, fine (though in practice they never do). If they want to be a gatekeeper for changes to that file they can fuck off.