If new, backwards compatible functionality is introduced to the public API. MINOR version Y (x.Y.z | x > 0) MUST be incremented If one library upgrades to the new 1.1.0 Cats before the other one does, yourĪpplication still runs thanks to this backward binary compatibility.Īlso worth noting is that according to semantic versioning, This is critical when your application has a diamondĭependency on Cats - depending on two or more libraries that all depend on Cats. the new JAR will be a drop-in replacement for We will maintain backward binary compatibility between PATCH AND MINOR versions.įor example, when we release Cats 1.1.0, it will be backward binary compatible In semantic versioning, backward breaking change is ONLY allowed between MAJOR versions. Thus, we treat backward binary compatibility maintenance with a high priority. Java and Scala libraries (including the Scala lang).Ĭats strives to provide a solid and stable foundation for an ecosystem ofįP libraries. Going forward, which is different from the scheme common among If you are being harassed, please contact one of us Hope to avoid letting minor aggressions and misunderstandings escalate That fails to live up to our expectations, you should disengage andĬontact one of the project maintainers in private. You find yourself embroiled in a situation that becomes heated, or We hope that our community will be respectful, helpful, and kind. Please join us!ĭiscussing Cats on GitHub, Discord, or other venues. The Typelevel Discord has #cats and #cats-devĬhannels, as well as community channels such as #beginners.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |