UPDATE I totally get why this question could/should get dinged ... but hey, if you feel inclined to vote down this question, can you also provide some feedback on where a better forum could be for me to take this question?
I am at the start of a new effort to create an internal product for my company. So, right off the bat, the stakes aren't crazy high since my customers are my co-workers across the org (I personally work with a team of 8 developers).
Our main focus is to combine our multiple (~4) services under one, unified product (so a lot of refactoring, merging, and complete rewrites of code).
We're starting to cobble together the plan/strategy for this new product and I've been questioning a lot of our existing strategies to see if there is an advantage to another approach.
When is it appropriate to have scheduled releases (vs. pushing to prod when a sizable effort has been completed) ?
A stakeholder asked me about a release schedule and my first thought was, "Why don't we do this?"
We can definitely continue with ad-hoc pushes, but is there a value-add to telling the business owners/stakeholders that they should be able to expect a release every third Monday of a month (for example)?