How to decide when to declare a new SRFI draft
John Cowan
(09 Aug 2020 17:35 UTC)
|
Re: How to decide when to declare a new SRFI draft Lassi Kortela (09 Aug 2020 17:51 UTC)
|
Re: How to decide when to declare a new SRFI draft
Lassi Kortela
(09 Aug 2020 17:54 UTC)
|
Re: How to decide when to declare a new SRFI draft
John Cowan
(09 Aug 2020 18:01 UTC)
|
Re: How to decide when to declare a new SRFI draft
Lassi Kortela
(09 Aug 2020 18:23 UTC)
|
Re: How to decide when to declare a new SRFI draft
(no sender)
(09 Aug 2020 19:14 UTC)
|
Re: How to decide when to declare a new SRFI draft
Lassi Kortela
(09 Aug 2020 19:35 UTC)
|
Re: How to decide when to declare a new SRFI draft
hga@xxxxxx
(09 Aug 2020 19:55 UTC)
|
Re: How to decide when to declare a new SRFI draft
Arthur A. Gleckler
(09 Aug 2020 21:39 UTC)
|
Re: How to decide when to declare a new SRFI draft
(no sender)
(18 Aug 2020 06:53 UTC)
|
Re: How to decide when to declare a new SRFI draft Lassi Kortela 09 Aug 2020 17:51 UTC
If each change to the public interface in the Specification section necessitates a new draft, is that too often? Of course an author can batch many interface changes into the same draft. I feel we're grappling with a very similar question as the inventor(s) of semantic versioning (https://semver.org). The semver rule is: - Increment major version when you make incompatible API changes. - Increment minor version when you add functionality in a backwards compatible manner. - Increment patch version when you make backwards compatible bug fixes. In semver terms, my suggestion would be that each major version requires a new draft.