update version policy to use effver

[d-v-b]

This changes the versioning policy from something semver-ish to effver.

based on conversations in this issue

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

closes#2889

[jhamman]

Thanks @d-v-b -- this looks great!

[d-v-b]

@zarr-developers/python-core-devs it would be good to get yalls eyes on this

[dstansby]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

[d-v-b]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

@dstansby have a look at the content I added in b90f0ef

[d-v-b]

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

[sanketverma1704]

Thanks for working on this, @d-v-b! Important change.

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

We should at least make a social media announcement on BlueSky, LinkedIn, and Mastodon. A blog post would be great! I can take care of the announcements and help with blog writing/review.

A minor suggestion: Can we wrap the text to 80 (or similar) columns?

[d-v-b]

This changes the versioning policy from something semver-ish to effver.

based on conversations in this issue

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

closes#2889

[jhamman]

Thanks @d-v-b -- this looks great!

[d-v-b]

@zarr-developers/python-core-devs it would be good to get yalls eyes on this

[dstansby]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

[d-v-b]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

@dstansby have a look at the content I added in b90f0ef

[d-v-b]

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

[sanketverma1704]

Thanks for working on this, @d-v-b! Important change.

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

We should at least make a social media announcement on BlueSky, LinkedIn, and Mastodon. A blog post would be great! I can take care of the announcements and help with blog writing/review.

A minor suggestion: Can we wrap the text to 80 (or similar) columns?

[d-v-b]

This changes the versioning policy from something semver-ish to effver.

based on conversations in this issue

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

closes#2889

[jhamman]

Thanks @d-v-b -- this looks great!

[d-v-b]

@zarr-developers/python-core-devs it would be good to get yalls eyes on this

[dstansby]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

[d-v-b]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

@dstansby have a look at the content I added in b90f0ef

[d-v-b]

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

[sanketverma1704]

Thanks for working on this, @d-v-b! Important change.

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

We should at least make a social media announcement on BlueSky, LinkedIn, and Mastodon. A blog post would be great! I can take care of the announcements and help with blog writing/review.

A minor suggestion: Can we wrap the text to 80 (or similar) columns?

[d-v-b]

This changes the versioning policy from something semver-ish to effver.

based on conversations in this issue

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

closes#2889

[jhamman]

Thanks @d-v-b -- this looks great!

[d-v-b]

@zarr-developers/python-core-devs it would be good to get yalls eyes on this

[dstansby]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

[d-v-b]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

@dstansby have a look at the content I added in b90f0ef

[d-v-b]

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

[sanketverma1704]

Thanks for working on this, @d-v-b! Important change.

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

We should at least make a social media announcement on BlueSky, LinkedIn, and Mastodon. A blog post would be great! I can take care of the announcements and help with blog writing/review.

A minor suggestion: Can we wrap the text to 80 (or similar) columns?

[d-v-b]

This changes the versioning policy from something semver-ish to effver.

based on conversations in this issue

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

closes#2889

[jhamman]

Thanks @d-v-b -- this looks great!

[d-v-b]

@zarr-developers/python-core-devs it would be good to get yalls eyes on this

[dstansby]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

[d-v-b]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

@dstansby have a look at the content I added in b90f0ef

[d-v-b]

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

[sanketverma1704]

Thanks for working on this, @d-v-b! Important change.

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

We should at least make a social media announcement on BlueSky, LinkedIn, and Mastodon. A blog post would be great! I can take care of the announcements and help with blog writing/review.

A minor suggestion: Can we wrap the text to 80 (or similar) columns?

[d-v-b]

This changes the versioning policy from something semver-ish to effver.

based on conversations in this issue

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

closes#2889

[jhamman]

Thanks @d-v-b -- this looks great!

[d-v-b]

@zarr-developers/python-core-devs it would be good to get yalls eyes on this

[dstansby]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

[d-v-b]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

@dstansby have a look at the content I added in b90f0ef

[d-v-b]

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

[sanketverma1704]

Thanks for working on this, @d-v-b! Important change.

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

We should at least make a social media announcement on BlueSky, LinkedIn, and Mastodon. A blog post would be great! I can take care of the announcements and help with blog writing/review.

A minor suggestion: Can we wrap the text to 80 (or similar) columns?

[d-v-b]

This changes the versioning policy from something semver-ish to effver.

based on conversations in this issue

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

closes#2889

[jhamman]

Thanks @d-v-b -- this looks great!

[d-v-b]

@zarr-developers/python-core-devs it would be good to get yalls eyes on this

[dstansby]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

[d-v-b]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

@dstansby have a look at the content I added in b90f0ef

[d-v-b]

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

[sanketverma1704]

Thanks for working on this, @d-v-b! Important change.

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

We should at least make a social media announcement on BlueSky, LinkedIn, and Mastodon. A blog post would be great! I can take care of the announcements and help with blog writing/review.

A minor suggestion: Can we wrap the text to 80 (or similar) columns?

[d-v-b]

This changes the versioning policy from something semver-ish to effver.

based on conversations in this issue

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

closes#2889

[jhamman]

Thanks @d-v-b -- this looks great!

[d-v-b]

@zarr-developers/python-core-devs it would be good to get yalls eyes on this

[dstansby]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

[d-v-b]

Thanks for tackling this! I left some comments inline. I think a major gap in the policy as it stands is that it doesn't embody @TomAugspurger's excellent points of being considerate to downstream users by:

• preserving backwards compatibility where possible
• giving notice of deprecations through FutureWarnings
• giving users and libraries time to adapt to those deprecations

Matplotlib has some good guidelines on making breaking API changes using deprecations which could be taken as inspiration here.

@dstansby have a look at the content I added in b90f0ef

[d-v-b]

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

[sanketverma1704]

Thanks for working on this, @d-v-b! Important change.

does anyone else think a community announcement (e.g. a blog post) would make sense here? If so, I can start working on one

We should at least make a social media announcement on BlueSky, LinkedIn, and Mastodon. A blog post would be great! I can take care of the announcements and help with blog writing/review.

A minor suggestion: Can we wrap the text to 80 (or similar) columns?