I think Russ' feedback may imply dep needing to be versioned, as in the project itself publishing releases. Specially considering Peter Bourgon's lastest response, there's no way of users to know if dep is usable yet or not (roadmap is too abstract in that regard), and after that, what features made in. Is that a real concern or am I too off the mark here?
On Tuesday, March 28, 2017 at 5:39:06 AM UTC-3, Peter Bourgon wrote: > > On Tue, Mar 28, 2017 at 3:14 AM, Russ Cox <r...@golang.org <javascript:>> > wrote: > > On Mon, Mar 13, 2017 at 5:09 PM, Russ Cox <r...@golang.org <javascript:>> > wrote: > >> > >> By far the most important things to do with dep right now are (1) build > >> something people can use and get benefit from today and eliminate > blockers > >> to adoption and (2) based on experience with that usage, learn what the > >> eventual design and go command integration should look like. > > > > I've been away and am not fully back yet, but I want to reemphasize > these > > two lines, for everyone on this list and anyone else reading. I've heard > a > > few people in various forums saying things like "I won't use dep until > it's > > official". > > > > Please don't wait. Use it now. Make it possible for dep users to depend > on > > specific versions of your packages: convert your packages to have > manifest > > and lock files, and add version tags to your repos. Use dep for your own > > projects, to find out how well the approach works. Let us know. > > Agreed! But one important addendum: please wait until we've merged in > the manifest/lock file format changes[0][1] :) I'll post another > update to this thread when that's complete, as well as update dep's > README to remove the warnings. Thanks! > > [0] https://github.com/golang/dep/issues/119 > [1] https://github.com/golang/dep/issues/168 > > > > This is all critical. If you wait to try any of this until it's in the > go > > command, then your feedback basically won't have any impact, because > things > > will be so much harder to change at that point. > > > > (The flip side of this is that dep should freeze these basic details so > that > > users aren't chasing a moving target. They don't need to be perfect. We > know > > that JSON is not perfect, for example, but it's fine for this trial. The > > goal is to learn about the overall experience and semantics offered, not > the > > file format.) > > > > Russ > > > > -- > > You received this message because you are subscribed to the Google > Groups > > "golang-nuts" group. > > To unsubscribe from this group and stop receiving emails from it, send > an > > email to golang-nuts...@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
