subject:"\[go\-nuts\] About Libraries Versioning"

Re: [go-nuts] About Libraries Versioning

2019-11-20 Thread Eyal

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 > > wrote: > > > The recommended way to create a new version for a go library is by > copying the

Re: [go-nuts] About Libraries Versioning

2019-11-20 Thread Jan Mercl

On Wed, Nov 20, 2019 at 2:42 PM Eyal 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

[go-nuts] About Libraries Versioning

2019-11-20 Thread Eyal

Hi The recommended way to create a new version for a go library is by copying the library code to a v2 directory. I am against this approach from the following reasons: 1. Code duplication: harder to back port fixes, harder to follow, not "nice".