Closed chrbayer closed 4 years ago
Thanks for this PR, @chrbayer - This looks like a nice update!
Thanks @chrbayer - I just did another pass and found just one minor thing. I need to test a bit, but so far the changes look good! I'll let you know how it goes with the tests,
@marcdumais-work Thank you very much for reviewing and testing. Please tell me if all tests and reviews are finished, so that I can include all findings in the PR. Should I make a sperate commit or just re-push fixed?
Should I make a sperate commit or just re-push fixed?
It's fine to force-push your fix(es).
Normally we prefer squashing the commits of PRs but in this case, looking a the commit messages, the breakdown looks logical and if you think you've maintained the changes pretty well insulated, each in their own commit, I have no problem retaining the various commits you have in the PR currently.
Though if we conclude it will make no difference in image size, we could return to a single cleanup at the end for apt temp files (i.e. drop last commit)
This PR introduces lots of changes, so it will be hard to test everything. I've done some sanity testing, just to confirm that the main things seem to still work. No issue found!
[full]:
[cpp]
[python]
@chrbayer Ready for your final update.
Can you let me know if anything substantial changes vs the current version, that would make it worth it to redo some of the testing?
@marcdumais-work Thank you very much for all you support! The only changes I did are the two proposed changes:
For me this PR should now be complete :-)
Where possible sync the single language images and the full images and the update versions of development tools in full and other images when in sync: