3 ms·
Speaking of names and versions -- while working on Cloud Foundry Buildpacks we frequently turned our brains into pretzels trying to manage what components were
by jacques_chester 9y ago
Speaking of names and versions -- while working on Cloud Foundry Buildpacks we frequently turned our brains into pretzels trying to manage what components were versioned how. We even had custom logic to parse a YAML file where we maintained a mapping to keep things straight.
Especially since some components embedded different versions of other components.
I don't know if the situation has improved since I rotated off, but a bog-ordinary semver scheme would've saved a world of pain.
Failing that, a single page with components (SDK? Runtime?) and available version numbers that gets updated.
Because we mostly wound up working what was what from forensic readings of scattered blog posts, Github release and I think comments on Github issues.
In any case, I am sure the team would be glad to give you feedback on their experiences since then -- my email is in my profile if want me to pass anything along.
- runfaster2000 9y agoSee: https://github.com/dotnet/designs/issues/2 https://github.com/dotnet/designs/issues/2
- jacques_chester 9y agoThankyou! I will ping my colleagues tomorrow.
- runfaster2000 9y agoBTW: Your friends can also contact me -> rlander@ms
- jacques_chester 9y agoThe thankyous keep rolling. I also remembered I can point you at the Slack instance where they live -- https://slack.cloudfoundry.org/ https://slack.cloudfoundry.org/, in the #buildpacks channel.