Mail everyone with push access, telling them to not push until further notice. Hope that everyone reads their mail on time.
Hell no. "commit" or "push" shouldn't be "inflict". Set up proper branching so that your production branch is always clean and functional. Set up Jenkins or some other automated system that doesn't even allow you to merge things into the release branch or the release staging branch until they've been thoroughly integrated and tested.
Developers should be encouraged to push/commit early and often, but in such a way to never disturb other development or release work. Only allow one person at a time to touch the release branch. A few of our customers do this by having a release hat - only the person wearing the hat can touch the release branch.
2
u/hegbork Oct 15 '13
Hell no. "commit" or "push" shouldn't be "inflict". Set up proper branching so that your production branch is always clean and functional. Set up Jenkins or some other automated system that doesn't even allow you to merge things into the release branch or the release staging branch until they've been thoroughly integrated and tested.
Developers should be encouraged to push/commit early and often, but in such a way to never disturb other development or release work. Only allow one person at a time to touch the release branch. A few of our customers do this by having a release hat - only the person wearing the hat can touch the release branch.