It's still not a 100% solution, but I think sourcehut is a good fit for CDE CI,
mostly because it directly supports running jobs on a wide array of Linux
distros *and* BSDs. It also works with just using their CI against a repo
hosted elsewhere (in our case, sourceforge). It does have 2 major sh
I'll change the wiki pages accordingly when I have the time (probs
tomorrow). I would suggest that once a major change has been done (like
recently solving the gcc 10 breakage) we test on all platforms and push out
a new source package. That way we've always got a safe release for new
users or peop
On 11/28/20 3:54 PM, Danilo Pecher wrote:
> Hi folks,
>
> May I offer a suggestion? We need something of a release strategy. We
> should depart from the "pull stuff from the git repo" strategy in the
> Wikis, because we keep breaking our build by pushing untested stuff.
>
> As I build CDE daily o
I agree, the wording should be changed to something like “Always use the
latest release, git builds can and do break often”. That line was from the
early days (I put it there) when the early releases were so fast moving
that the only way to get a build on your platform was to pull from git.
Now, it
