As part of the upcoming 3.3.0 release preparation — module documentation was updated in several places. Among other things module naming and versioning pages were added. Below you can find a summary of our suggestions. You can already browse the development version of the documentation. It will become the main documentation after the 3.3.0 release. Note You are free to use your own module name and versioning scheme, but standardizing on the same format will make it easier to reuse modules prepared by someone else.
Here we are with the next 3.2.0 release! This is generally a bugfix release with some additional usability improvements. Full changelog can be found here, below you can see highlights of this release. Better macOS support As part of development we added support for executing tests on macOS platform in our CI. This should make the macOS experience better. In the future we plan to make CEKit installation easier on this platform as well.
After 3.0.0 release we decided make our release cycle faster. We’re not afraid of new version numbers, you shouldn’t be too 😏 From now on you can expect new minor releases come out faster. These will be less feature-packed but on other hand this will let us shorten the time between a bug/feature report and the release containing the fix. Above introduction would be meaningless without a release, so here it is!
After initial 3.0.0 release we’ve done earlier this month we’ve gathered feedback and we found that some issues warrant a new bugfix release. Changes Learn more below about these fixes. Fixes in packages and modules installation in overrides In case packages or modules were defined only in overrides (the main image descriptor did not have any mention of packages or modules), these were ignored. This was fixed and now you can have a pretty much empty image descriptor and define your content in modules only.
Phew, that was quite some work, but we made it finally! We’re very happy to announce immediate availability of CEKit 3.0.0! Before we dive into details we would like to thank following people for their help on the release (no particular order) Jonathan Dowland; bug reports, testing, feedback Ken Wills, testing, feedback Nick Cross; contributions David Ward; testing, feedback It also a great time to thank David Becvarik, previous CEKit project leader, for his dedication to make CEKit a better project 👏 Thank you and good luck in your new role!
3.0 · development
We are very close to release CEKit version 3.0. This is a great time to discuss one of the biggest changes we made in the codebase in preparation for 3.0: the module merging process rewrite. Old style merging Since early days of CEKit all modules were processed and merged internally. What does it mean? Let’s imagine we have an image descriptor that requires a few modules to install. These modules can define anything what is available in the module descriptor.
3.0 · development
As part of CEKit 3.0 development we spend some time on reviewing existing 2.x code. Many areas were identified where an of improvements were identified and some of them were already adjusted! We plan series of blog posts about most important changes that will be part of CEKit 3.0. This is the first one. One of the parts that was under heavy review was the CLI itself. We found that the CLI was bloated and the usage was not clear at all.
A fresh bugfix 2.2.7 release is now out! One of our users found two issues related to artifact handling in the OSBS builder. See changelog below for issue details. CEKit 2.2.7 is immediately available for upgrade. Changelog Artifacts are not downloaded from unsuccessful builds in Koji, #415 Handling artifacts that specify target has been fixed in the OSBS builder, #414
It took quite some time to prepare it, but we finally made it! Welcome to the official CEKit website. You can expect to have the latest information related to the project available on this blog. The CEKit team will try to feed you with articles and guides to make the use of the project more pleasant. Besides this you will exactly know what’s cooking next in the development branch.