Skip to content

Changing the default branch of Zarr-Python #15

Closed

Description

@sanketverma1704

Considering the PRs opened by @grlee77 to add V3 in Zarr-Python, I and @joshmoore propose that we review and merge the PRs by @grlee78 into main and change the default branch to v2-main or something similar.

This will allow us to:

  • Move towards the development of stable V3
  • All the new PRs by the community and users will be opened into main which would have V3 features added by @grlee77. This would help us find any bugs/issues and fix them.

Thoughts?

Cc: @jakirkham @alimanfoo @rabernat @ryan-williams

Activity

  1. sanketverma1704 commented on Mar 5, 2022

    @sanketverma1704
    MemberAuthor

    Update: @grlee78's PR has passed all the checks and is ready for reviewing and merging.

  2. joshmoore commented on Mar 7, 2022

    @joshmoore
    Member

    change the default branch to v2-main or something similar.

    I'd like to clarify that in mind this sentence is "change the current default branch (i.e.master) to v2-something".

    Basically, there are three calls for objections (and/or requests for alternatives):

    1. Objections to renaming master to main on zarr-python per Switch master branches to main community#44?
    2. Objections to creating separate "stable" and "dev" branches? (Naming to be worked out)
    3. Objections to making the "dev" branch the default in order to drive the v3 work?
  3. joshmoore commented on Mar 10, 2022

    @joshmoore
    Member

    Feedback from today's call:

    Thoughts still welcome. 898 at least is unblocked, and a decision on this issue will only need to be made when the time for 2.11.2 comes.

  4. jakirkham commented on Mar 11, 2022

    @jakirkham
    Member

    Sorry for missing the call. Was out sick most of the week.

    Sounds like the branch versioning issue is less pressing.

    In case there is still a need for branch versioning, would suggest we consider an approach where the non-latest major version branch is broken out (v2) and main points to the latest major version.

  5. sanketverma1704 commented on Dec 20, 2022

    @sanketverma1704
    MemberAuthor

    Is it safe to close this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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