Open jonahgraham opened 3 months ago
I always found using milestones builds to be a better compromise for downstream projects (not Platform/SDK devs). It is less frequent and you also have the benefit of possibly less dependency hell from simrel. It makes also bisecting more likely to work across more commits (it's still not perfect, I'd rather pin to a specific milestone and have them retained forever but AFAIK that's not the case).
We keep going back and forth on tracking latest I-build of platform, or specific builds of platform. Our current iteration is on latest I-build:
https://github.com/eclipse-cdt/cdt/blob/6b14816318494ac6240539bcd7dc50fa2e721e0f/releng/org.eclipse.cdt.target/cdt.target#L10
This means that changes in platform that break our build are quickly picked up - a good thing. But it means that the build is broken for contributors when they make a PR - a bad thing.
We need a better balance so we can keep benefiting from good things, without making it sucky for contributors.
Perhaps a daily build of CDT with email notifications would be an improvement?