It is solved -- just not widely employed. There is no official stance on package versions, because the core Go development doesn't really need/use it. The Go

It is solved -- just not widely employed. There is no official stance on package versions, because the core Go development doesn't really need/use it. The Go 1 compatibility guarantees no backwards incompat changes to stdlib. Experimental package development occurs at golang.org/x/foo ("x" for experimental, presumably). Those packages are unstable, and there are no versions. If they change at all you have to update. People follow the 'official' approach blindly, but aren't experienced enough to know what the tradeoff's in the official approach are.