Of coarse, sorry for not mentioning it. I still think that this is a major issue.
On Wednesday, November 20, 2019 at 3:47:25 PM UTC+2, Jan Mercl wrote: > > On Wed, Nov 20, 2019 at 2:42 PM Eyal <pos...@gmail.com <javascript:>> > wrote: > > > The recommended way to create a new version for a go library is by > copying the library code to a v2 directory. > > Only if the new version that breaks backward compatibility. Bug fixes > and/or new features do not need such switch. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/d0b49ee2-e666-4cdb-b862-024a99c8d236%40googlegroups.com.
