April 7, 2015 at 9:58 pm
Comments posted to this topic are about the item Release Wednesday
April 8, 2015 at 2:23 am
I am currently involved with one client's less frequent deployment cycle. They are looking to move to a more flexible and frequent delivery but they have a reasonably large connection of related system. They are in an industry that is heavily regulated which adds its own complications.
The first step is continuous integration (CI) as without it the development teams cannot have the confidence in the build.
Next step, in my opinion, a higher coverage level by automated testing azs part of the CI.
Gaz
-- Stop your grinnin' and drop your linen...they're everywhere!!!
April 8, 2015 at 6:47 am
Our deployments are monthly. I wish they were more frequent. We develop for our own in house use. I remember when we had immediate updates. If there was a bug it got fixed right then. Each screen was its own exe file and you just had to get people out of that screen to update it. Now it's all one big huge program. Deployments happen at night when everyone is gone except a few IT staff. The cycle of life of bug to fix to test to deployment (with a few re-dos in the middle) works but the best we seem to be able to do is once a month. I would imagine there would be a little re-figuring out how to handle the VCS check-ins. But I believe it possible to get down to more frequent deployments. Oh for the good old days when I could just fix a bug or make a change now, whenever I wanted/needed.
April 8, 2015 at 7:37 am
Agreed, I know of a company that went from a Tuesday and Friday release schedule to a Monday and Thursday instead. No one wants to roll out changes at 4PM on a Friday.
----------------------
https://thomaslarock.com
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply