Apps

Poll: What kind of release cycles do you use?

Are your release schedules planned (short-term or long-term), infrequent, a mix, or ad hoc? Let us know by taking this poll.

I've been working on a variety of projects with different release styles lately. Some projects are fairly "catch as catch can," where I do work, test, and release it to production when we are happy. I have one project that is working with a weekly iteration cycle, where we deploy to Production once a week, and patch showstoppers mid-week as needed. I know some people who also use an iterative approach, but their iterations are in months or even quarters. And I have projects operating on more traditional, infrequent, large releases on an "it's done when it's done" basis. What kind of release schedule are you using, and what do you think of it?

J.Ja

About

Justin James is the Lead Architect for Conigent.

3 comments
Realvdude
Realvdude

I'm sure the options and combinations are endless. In our case we release "as needed/as completed", but try to have a release every quarter. The releases tend to be small, except where major application functionality has been added or updated.

Slayer_
Slayer_

So the best of all worlds. Usually first our big release, then a month or two later, we release a followup to fix reported problems. And that sits, sending weekly as needed updates for minor changes. and Ad-hoc updates for serious show stopping bugs. And significant new features are released in the next big update.

Editor's Picks