I am a developer at The Washington Post and I help build newsroom facing tools. I also am the Chair of the DC chapter of ACM and produce a podcast called DC Tech Stories.
I have been here since Jan so I am not a big part of the priority setting for our team. Some of our work are hot fixes and are deployed ALL the time, some take months of prep, planning, and dedicated sprints, I would say a 50/50 mix of those two things.
I am a developer at The Washington Post and I help build newsroom facing tools. I also am the Chair of the DC chapter of ACM and produce a podcast called DC Tech Stories.
Depends on the team and tool (can I copy and past that to every answer hahah). Most of the time it's branch off master, fix bug, deploy to QA/testing site, test again, get your PR approved by whatever teams are involved, deploy to master, deal with the cache :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is our latest too and I think it is AWESOME: washingtonpost.com/pr/wp/2017/09/1...
I have been here since Jan so I am not a big part of the priority setting for our team. Some of our work are hot fixes and are deployed ALL the time, some take months of prep, planning, and dedicated sprints, I would say a 50/50 mix of those two things.
What's the process for getting a hot fix into production?
Depends on the team and tool (can I copy and past that to every answer hahah). Most of the time it's branch off master, fix bug, deploy to QA/testing site, test again, get your PR approved by whatever teams are involved, deploy to master, deal with the cache :)