Hi @xet7,
I'm one of the app packager of Wekan for YunoHost. And the link to the original post I made : https://github.com/YunoHost-Apps/wekan_ynh/issues/54#issuecomment-537271009
First I have to say a big thank you for the hard work you have already done to the awesome Wekan. It was just the app I was looking for to manage my work on YunoHost. And thank to having took the time to respond.
My bad for the changelog, I didn't seen it exists. I used to go on the releases page (https://github.com/wekan/wekan/releases ) of the repository to find the information. But now I know ^^
Regarding the number of releases, sometimes there are 9 releases a day (V3.27 to V3.35 on 2019-08-29).
As I'm not a developer, I'm not a good juge..
I don't know if it's because Wekan is still developing but from YunoHost perspective we use to package apps with longer release cycle (Mastodon: v3.0.0rc2 / 137 releases; Peertube: v1.4.1 / 76 releases; pixelfed 0.10.6 beta / 19 releases)
Or maybe it's the way we package Wekan for YunoHost.
YunoHost plans to provide apps for selfhosting. Hosting from a RaspberryPi (arm and arm64) to servers or virtual servers (amd64). Having YunoHost users installing apps with one clic...
We don't package using .deb package or snap or docker. We do it like a manual installation.
At the beginning we packaged directly from the sources and since you provided builds at https://releases.wekan.team/, we use them to improve installation reproductibility and reduce installation time.
When I discovered https://releases.wekan.team/raspi3/, it was just perfect for us to be able to install wekan on raspberry Pi arm64 from an already built version.
So for packaging wekan, we use a link to the builded .zip files (amd64 and arm64), having a sha256sum of each release file to be sure they are not altered.
A first point is: as each built is not kept at https://releases.wekan.team/, we have to download them and upload them on our own website to keep them available.
A second point is: as there is no new raspberryPi since 2.94, it difficult to upgrade the whole package for YunoHost
A third point is: for each Wekan release we have to make changes in our own package.
So the effort for maintaining the wekan package up to date is high for us.
I don't know how other applications do and if it can be automated but some are able to provide builds with the release sources:
Or maybe we should go back to package from the source file.