4 ms·
Change freezes have more uses than the OP has highlighted. We've just had Christmas and Boxing Day. There may be less support staff available on those days, an
by tezza 12y ago
Change freezes have more uses than the OP has highlighted.
We've just had Christmas and Boxing Day. There may be less support staff available on those days, and the devs may be on holiday.
By having a change freeze beforehand, the set of things that have changed is reduced, so any issue that arises will be easier to diagnose.
Less changes allows a firm to justify the lower support overhead... not eliminate it
- sargun 12y agoI'd say that's a straight up work freeze, not just a change freeze.
- minot 12y agoNot quite a work freeze. There is a subtle difference in that only the most critical code fixes will go in, we'd just document everything else and come up with solutions for the rest. So this isn't exactly a 100% code freeze. There are still critical fixes that might go in with managerial understanding and approval. The downside is people then start saying things like "my fix doesn't require any code changes, only SQL changes." I am not trying to be pedantic and say SQL is code, which it is, Rather, if the change could be done better in C# but we do a workaround in the database layer, that isn't exactly ideal.