Sometimes you gotta go for it and release on a Friday! 
It’s a hot topic. Some people do and some people don’t and it comes with a lot of “it depends.”
So I’d love to know…
What’s your definition of releasing on a Friday?
4 Likes
We’d release on a friday if it was up to us. But my boss is scared of Monday morning complaints so we don’t do it.
In a well planned out process, it shouldn’t be a problem as one would always have a fallback in place.
3 Likes
I’m a fan of releasing blog posts on a Friday. Though, truthfully, I don’t even do that. I release mine on Wednesday. 
Still trying to think of what I do release on Fridays.
Oooh, what if we did meme releases?
2 Likes
Releasing on Friday is a bit like Marmite. People seem to love or hate it.
1 Like
If there is fear of releasing on Friday, then you likely have a quality problem, or at least an opportunity for improvement. Perhaps ask why not release? Or why is Friday special? Look for things like: do we not release every day? Maybe more than once a day? Are our batch sizes too big? Do we distinguish between release and deploy? (In which case this is really about deploying on Friday to me)
2 Likes
Depends on the context of the business and size of the team.
Context- work in community sport. We don’t release before the weekend, as Fridays/ Saturday’s are typically busy periods for users running events on weekends. reliant on exporting out entries, reports etc from the site. Otherwise - we prob would 
1 Like
I believe it’s okay to release on Friday but only if there is someone in the team as backup, because no matter how carefully we test the software and ensure the quality still there may be issue that may block the access.
For e.g. while i was working as a tester in a project then earlier the client had said that they don’t want dot in first name or last name of their users, but then we release the build and just in friday night their users having dot in names were blocked which they had not anticipated, so we had to do hotfix and it almost take whole friday night to hotfix, testing the regex , sanity and then deployment.
So it was possible because we were available else client and their users would remain blocked till monday morning.
There are people who see the deployment on friday as confidence in their build, however the quality of build should not be judge by the day but by the experience user has while using the app.
1 Like
Minor releases on a Thursday; major releases and cutover / deployments on a Saturday morning through to Sunday evening.
Context: SAP implementations, manufacturing, sales and distribution.
1 Like
from a tester’s point of view, “Limited time and weekend chaos”. However, It all depends on the project and team collaboration. Releasing it on friday is a nightmare scenario for testers. In case of any critical defects slips through, testers might have to work over the weekend to verify fixes.
1 Like
I think it depends a lot on the maturity / stability of the release process, and others surrounding it. For me, being able to release “boringly” on a Friday is something to aim for. On the other hand, avoiding it still reduces risk, assuming everyone takes weekends off. So maybe there’s a difference between, “we could if we wanted to, and it wouldn’t be a big deal,” and, “we could, but we’d rather add one more layer of risk mitigation”.
1 Like
Release on the day when a support development engineer is planned to be unavailable for a longer period of time than usual and no one is able to react to a potential business impacting production system issue.
1 Like
Bugs dont take weekends off!!
Watching PROD like a hawk and hoping nothing crashes. 
1 Like
All releases on thursdays.
1 Like
Releasing on Friday means, be ready for the weekend support 
1 Like