3
submitted 1 year ago* (last edited 1 year ago) by melroy@kbin.melroy.org to c/updates@kbin.melroy.org

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

top 5 comments
sorted by: hot top controversial new old
[-] Szwendacz@kbin.maciej.cloud 1 points 1 year ago

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 points 1 year ago

It's indeed a good idea to follow the develop branch until further notice.

[-] Szwendacz@kbin.maciej.cloud 1 points 1 year ago

Damn, seeing latest commits to branch I guess it it time for another update of my instance.

[-] melroy@kbin.melroy.org 1 points 1 year ago

I indeed made some... Improvements.. ๐Ÿ˜…

[-] vintprox@kbin.melroy.org 1 points 1 year ago

Haha, that aged well, didn't it? Join Mbin :)))

this post was submitted on 18 Jul 2023
3 points (100.0% liked)

Mbin Blog Updates

1 readers
1 users here now

Blog updates for Mbin (fork of /kbin). Upcoming features, issues or anything else related Mbin or the fediverse.

Just follow this magazine to keep yourself up-to-date!

founded 1 year ago
MODERATORS