Whenever this happens, and there are breaking changes to a module, either the major version of the module is bumped ( 1.x.x to 2.x.x, etc.), or a new module is created bumping the version in the module name ( terraform-wood-api-v1 to terraform-wood-api-v2, etc.). We try to make these changes as infrequent as possible by preferring deprecation annotations and the addition of new apis over the flat out removal of existing apis, but there always comes a time when it becomes burdensome to continue to move forward a deprecated api and it eventually has to be removed. Basically, anything that causes a developer to have to do work in order to update their usage of a Terraform module. Examples of this include the removal of a deprecated api, the removal of parameters in a method, etc. Occasionally, we need to release changes to a module that break the existing visible surface of the api. It should always be safe for developers to update a Terraform module to the newest patch version value because changes in the patch version should never modify the visible surface of the api. If implementations change, or features are added that don't change the visible surface of the api, those changes are indicated by bumping the patch version value ( x.x.1 to x.x.2, etc.). It should always be safe for developers to update a Terraform module to the newest minor version value because changes in the minor version should only ever expand the visible surface of the api. Whenever new features are added to one of our modules in a way that expands the visible surface of the api we indicate support for those new features by bumping the minor version value ( x.1.x to x.2.x, etc.). When developers update game versions they should check this repository to see which new major version corresponds to the new game version. Whenever a new version of the game is released we update each Terraform module and indicate that it is for a new version of the game by bumping the major version value ( 1.x.x to 2.x.x, etc.). Like all Fabric/Quilt mods and libraries, Terraform utilizes the semver system of versioning. When developing Terraform modules we try to keep a very strict versioning system to make using the api easy for mod developers. ModImplementation "-api:terraform-wood-api-v1:1.0.1"įor version information and specific module names use the maven navigator. "In a new 'galaxy brain' novel, it's AD 59,000 - and we're still kind of a mess". " 'The Terraformers' is a dazzling look at the distant future".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |