Yes you heard that right, we are planning for the first /kbin release. Currently most server admins are running directly from the develop branch since /kbin is still in very (early) active development.
That being said, we are planning for creating the first tagged released of /kbin! We still merge several pull requests, but holding off a bit. At the same time we are looking at all the high priority issues, seeing if some of those can be resolved or mitigated before the first tagged version.
I already introduced some basic CI/CD Workflow Actions within Codeberg. Also Ernest setup several development environments. All these preparations are necessary to achieve a better, faster and more stable release cycle in the near future.
Thanks to all contributors and of course @ernest and @piotrsikora. Thank you all for this wonderful community and becoming part of it.
~Melroy
5 Comments
Szwendacz@kbin.maciej.cloud · 1 pts · 3y
Stable release seem a really good idea to help bigger instances keep stable, as that is what users probably want. Meanwhile mine likely will follow devel branch :]
melroy@kbin.melroy.org · 1 pts · 3y
It's indeed a good idea to follow the
developbranch until further notice.Szwendacz@kbin.maciej.cloud · 1 pts · 3y
Damn, seeing latest commits to branch I guess it it time for another update of my instance.
melroy@kbin.melroy.org · 1 pts · 3y
I indeed made some... Improvements.. 😅
vintprox@kbin.melroy.org · 1 pts · 2y
Haha, that aged well, didn't it? Join Mbin :)))