3 ms·

This is interesting. I have been wondering about the viability and communuty interest in a service to enable subscription service for CI/CD systems at the proje

This is interesting. I have been wondering about the viability and communuty interest in a service to enable subscription service for CI/CD systems at the project level. OSS maintainers don't have a unified mechanism to alert packagers of updates. In place of a dirty hack to power IFTTT and Jenkins from fetchmail scripts when there is an announcement, we could have intelligence and transparent automation at the distro-level. Maintainer patches a 0-day, and there's a mad scramble for everyone to patch, test, package and publish. I would rather not wait on Debian to release a distribution or be forced to cherry-pick from Sid. OpenSolaris and OpenBSD could have feature parity with Cygwin and Alpine. We could have concurrent versioning, automation and container and filesystem-based deployments become a little less risky. Less focus on Vendor, more on Developer.

icebraining 9y ago
Debian has vcswatch to keep track of updates. I think it only works if the upstream repository keeps the Debian control files updated, but keeping track of commits that update a generic CHANGELOG file should be simple. That said, I don't think the vendor can be avoided unless you want to live on the edge. If you're on a released version of a distro (otherwise, you wouldn't have to cherry-pick from Sid), chances are you're not on the latest version of the software, and the patch has to be backported by the distro maintainer to version you are actually on.
andrey_utkin 9y ago
> OSS maintainers don't have a unified mechanism to alert packagers of updates. Gentoo developers have http://euscan.gentooexperimental.org/ http://euscan.gentooexperimental.org/ . Quite some automation is on the way to come soon.