Jérôme, Semantic Versioning 2.0.0 https://semver.org/#semantic-versioning-200
How should I handle deprecating functionality? https://semver.org/#how-should-i-handle-deprecating-functionality Deprecating existing functionality is a normal part of software development and is often required to make forward progress. When you deprecate part of your public API, you should do two things: (1) update your documentation to let users know about the change, (2) issue a new minor release with the deprecation in place. Before you completely remove the functionality in a new major release there should be at least one minor release that contains the deprecation so that users can smoothly transition to the new API. Peter On Friday, October 9, 2020 at 2:40:58 PM UTC-4, Jérôme LAFORGE wrote: > > Hello Gophers, > From your point of view, is it acceptable to deprecate (// Deprecated: > xxx) a function or something else into a Module with the change on its > patch version number? (from 1.0.0 to 1.0.1). > > Thx in adv > Best > Jérôme > -- 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/aba12ceb-d310-48be-a325-426d01c82549o%40googlegroups.com.
