With version 3.0 of the automation tool, the Unsibly community has finally clarified the path to independent development cycles and a modular system. In terms of code, version number itself is a very significant invention: Uncible 3.0 differs fundamentally in functionality from its predecessors.
Nevertheless, it marks the end of a major alternative phase, which has already been produced in previous versions 2.9 and 2.10 and is now complete, as the approval process for individual components must be developed independently of each other in the future, rather than pre-linked to each other. Unsibil 2.9 introduced collections as a distribution mechanism for Unsibil components, version 2.10 later splitting the main part of the previous distribution into a set of Unsible-base and additional collections.
Pay attention to the version number when updating
With Release 3.0, Unsibile is now a meta-distribution that only defines the exact versions of the packages in it. Accordingly, the version number of the whole package no longer follows Unsupply-base, and its current version number is still 2.10. Rather, it is based on the principle of the semantic version. New small releases appear every three weeks, which contain only backward-compatible changes. Changes that do not match the scheduled major releases are assigned every six months.
Development is currently moving at a rapid pace. The next major Unsubscribe release is scheduled for May 4.0. It must be based on version 2.11 of the basic functions later renamed Unsible-Core to Unsible-Core. The current Unseable 3.0, on the other hand, is satisfied with the Unseable Base 2.10 released last fall. It provides the following overview:
- Compatibility 2.9: All-in-one, Technology Preview Collections
- Compatibility 2.10: Unspecified-base and split into collections
- Unspeakable-Core 2.11: Renaming Unzip-Base to Unseen-Core (not yet available)
- Unseen 3.0: Community package, based on Unseen-Base 2.10 + packages
- Unsipil 4.0: Community Package, with Unzip Core 2.11+ packages (not yet available)
Some technical changes
In addition to fundamental organizational changes, Unseable 3.0 also features some technical innovations. For example, a separate module takes care of user-specific ssh settings. Anyone who runs a container site based on Kubernet can now manage hem packages through Unsip through the appropriate modules. Additionally, a new Connect plugin performs tasks in Toker containers and additional search plug-ins make it easier to handle complex variables. The Changelog Zoo Unseen 3.0 Contains a complete list of all changes.