We'll none of that here
Lessons learnt - well, we wrote them down and put that into the Document Store (cue choir of angels)
Then, TRADITION!
Each time a New Project to build The Next Generation of our product has started, the New Team has chucked away all of the preceding versions' work, including any tooling that may have been created to get the job done: "Everything important is in the new deliverables spec". Which, once again, only tells us what the customer will see, not how we got there.
Cross-platform Makefiles with features to fit our procedures (and extra builtin help)? Nah, we want to just start small, no need for all that. Put this guy on it; ignore that he has just googled all the basic how-to's and manuals that are already in this directory on the server.
Collection of OSS libraries that we've built on all the platforms already and have sorted by licence, collected in one tree and shared from there? Nah, to Github we shall go again; ooh, look, Fred's branch has a copy of the same library I'm just downloading, that makes the fourth different version of it in our new repo. Didn't the author change the licence from MIT to GPL at some point? What fun!
Compact scripting language? Nah, this one is all the fashion - see, yours doesn't even have has half as many books written about it!
You have a tested Over-The-Air firmware updating tool? Cool, always wanted to write one of those! Don't understand that the cryptographic signing though, but XOR is good enough.
Tool to generate Open Source compliance document? Doesn't work with our new build but don't worry, we can just do it manually in Word as we go along. So, did we use Fred's branch in the end?
Copy to go into escrow? Easy peasy, our build just gets all these libraries fresh from Github, no need to put *them* onto CD/USB, they'll always be there. Don't be so old-fashioned.
(At this point, I may be getting a bit ranty, so shall stop and lie down for a bit)