So i got a lot of upstream responses about their golang version requirements. It looks like nobody is willing to commit to a specific version and everybody just does something without documenting it.
That's a really sad state of affair for downstream packagers.
I think we should adopt a specific policy. golang has a release every 6 months, and supports only release N and N-1.
I think a reasonable plan going forward would be to target golang release N-1 to maximize distribution, or release N at least 2-3 months after release so it has time to reach users. In any case, "stable" distros will apparently never be targeted by matterbridge, even though it saddens me. Whatever decision we make, this decision needs to be explained in the README so that users are not confused by us requiring very recent software.
Any opinions about this?
So i got a lot of upstream responses about their golang version requirements. It looks like nobody is willing to commit to a specific version and everybody just does something without documenting it.
That's a really sad state of affair for downstream packagers.
I think we should adopt a specific policy. golang has a release every 6 months, and supports only release N and N-1.
I think a reasonable plan going forward would be to target golang release N-1 to maximize distribution, or release N at least 2-3 months after release so it has time to reach users. In any case, "stable" distros will apparently never be targeted by matterbridge, even though it saddens me. Whatever decision we make, this decision needs to be explained in the README so that users are not confused by us requiring very recent software.
Any opinions about this?