8000 define our deprecation policy · Issue #2924 · zarr-developers/zarr-python · GitHub
[go: up one dir, main page]

Skip to content
define our deprecation policy #2924
Open
@d-v-b

Description

@d-v-b

An update to our versioning scheme is pending in #2910. That PR spawned a necessary discussion about what deprecation policy we should have. This also relates to the question of our release schedule. We can use this issue to figure these things out.

cc @dstansby

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0