loading...

Share your thoughts about code freezing

frozonicapp profile image Frozonic ・1 min read

In the last few days we've been getting feedback around how code freezing sort of flows in the opposite direction of Continuous Integration, which is not false, it does break it in a sense. But we also believe that for certain situations it is desired to stop merging code into production, here are a few examples:

  • When young products are being demoed in events.
  • When Mobile dev teams are submitting an app version for approval in the different application stores.
  • When infrastructural changes are being made. (i.e. server migrations, database engine migrations, etc.)
  • When apps need to be reviewed out, or audited for compliance purposes.

Do you agree with these? There could also be a lot more scenarios in which code freezing might be a good idea or strategy, but we would love to hear from you.

  • Do you think this is a relevant topic or discussion to have?
  • Do you think sometimes it is ok not to follow a principle completely? (like CI/CD for instance).
  • What do you think in general about this topic?

Please share your thoughts!

Happy Wednesday!

Posted on by:

frozonicapp profile

Frozonic

@frozonicapp

Code freeze management for your repositories

Discussion

pic
Editor guide
 

@ben mind sharing your thoughts!?