Re:Go vgo: Semantic Versioning and Human Error
by kardianos on Monday May 21, 2018 @05:26PM
(#17121970)
Yes, it is amusing that this objection to the vgo proposal are only now coming forward when it was proposed 2018-03-20, 2 months ago, and the design document a month before then.
[ Parent
| on HN ]
Re:Go vgo: Semantic Versioning and Human Error
by sagichmal on Monday May 21, 2018 @05:31PM
(#17122010)
Russ and the core team ignored the dependency management issue for years, and only responded to the community-led `dep` initiative after a year and a half. The `vgo` proposal was something like a hundred pages of dense technical details, and Sam has a full-time job. I think the sense of urgency you're implying is both artificial and unfair. It's been years already; we can wait another month or two for the details to shake out.
Re:Go vgo: Semantic Versioning and Human Error
by geodel on Monday May 21, 2018 @08:03PM
(#17122847)
> The `vgo` proposal was something like a hundred pages of dense technical details, and Sam has a full-time job
Does that mean 2-3 months are not enough to read 100 pages document and respond specially from people who are most concerned about package management? Or that Sam should be the only one to respond to this?
Re:Go vgo: Semantic Versioning and Human Error
by nemo1618 on Monday May 21, 2018 @05:52PM
(#17122159)
>The `vgo` proposal was something like a hundred pages of dense technical details
Which document are you referring to? The one linked in https://github.com/golang/go/issues/24301 is only about 600 lines: https://github.com/golang/proposal/blob/master/design/24301-...