Skip to content

Process for managing patch releases vs minor releases #260

Closed

Description

@darrelmiller

Up to this point we have used master as the primary branch that all releases are derived from. Now that we have a 1.0.0 release we have the potential for two distinct release branches.

We have bug fixes that should go into a 1.0.1 release and we have 1.1 work that should be released as a 1.1.0-preview nuget.

My proposal is that we continue using master for doing gated check-in's of the latest preview. When there are bug fixes to do on an existing release, we should create a branch based on the release tag and merge patches into that branch. We should then do a patch release from that branch.

Does that make sense? /cc PerthCharern Sam Xu (@xuzhg) Shweta Patil (@Shwetap05)

Should we do gated check-ins to the release-v1.0.x branch? I don't know how to set that up.

Activity

  1. Shwetap05 commented on May 17, 2018

    @Shwetap05
    Member
  2. PerthCharern commented on May 17, 2018

    @PerthCharern
    Contributor
  3. darrelmiller commented on May 17, 2018

    @darrelmiller
    MemberAuthor

    That works for me.

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