DEV Community

Discussion on: 5 reasons to start staging your code right now

Collapse
 
hollyw00d profile image
Matt Jennings

My company goes a step during our process of deployment including deploying to the following websites:

  • DEV (AKA "development"): Another developer reviews and a project manager (non-developer) NEVER reviews
  • STAGING: A developer and project manager reviews
  • PROD (AKA "production" or the live site): A developer and project manager reviews

Also we have protected (can't be deleted) git branches called:

  • develop
  • staging
  • production
Collapse
 
roberts profile image
Robert Schleinhege

Sounds interesting. How do you structure and store feedback between the project manager and the responsible developer? @hollyw00d

Collapse
 
hollyw00d profile image
Matt Jennings

@roberts we message the responsible project manager to view a link in a STAGING environment. Often I also sent them an IM (Instant Message) message as well to ensure they receive it.

Then if the responsible project manager approves the link in a STAGING environment that we push the work live (AKA deploy to PROD).

Thread Thread
 
roberts profile image
Robert Schleinhege

Makes sense. So an automatic notification for the project manager whenever a Staging environment was created/updated and a tool integration where the project manager could drop documented feedback and e.g. annotate screenshots would feel overeingineered? @hollyw00d

Thread Thread
 
hollyw00d profile image
Matt Jennings

We don't have an automated system yet to contact a project manager for to review work that is pushed to STAGING. That would be a great idea.