# Dealing with "breaking changes" when evolving a Software

**URL:** <https://forum.babylonjs.com/t/dealing-with-breaking-changes-when-evolving-a-software/55423>\
**Category:** Off topic\
**Created:** [December 17, 2024, 11:16am UTC](https://forum.babylonjs.com/t/dealing-with-breaking-changes-when-evolving-a-software/55423 "2024-12-17T11:16:30Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![brianzinn](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/brianzinn/32/28013_2.png) [@brianzinn](https://forum.babylonjs.com/u/brianzinn)\
**Post date:** [December 17, 2024, 9:23pm UTC](https://forum.babylonjs.com/t/dealing-with-breaking-changes-when-evolving-a-software/55423/9 "2024-12-17T21:23:10Z")

</div>

> [@Deltakosh](#):
>
> That’s something we can do more! This is a great idea honestly!

Not to be too ceremonial, but would be nice to see as a contributing guideline perhaps.  
Originally I posted it here 2020!! ( [@since tag versioning - Questions - Babylon.js](https://forum.babylonjs.com/t/since-tag-versioning/14393))

edit: just want to add that it’s helpful for new features as well, so people know min version to upgrade to get new feature.

---

_[View the full topic](https://forum.babylonjs.com/t/dealing-with-breaking-changes-when-evolving-a-software/55423)._