Skip to content

Change process for landing commits on v4.x-staging #90

@MylesBorins

Description

@MylesBorins

Currently we only cherry-pick commits to v4.x-staging that have been in a release for at least a week.

Alternatively we could land any commit once it has been approved for LTS. In this sense we would treat v4.x-staging very similarly to the way in which we treat master for cutting v5.x releases.

This does potentially introduce a higher probability of conflict when making releases, especially if we no longer rebase v4.x-staging. It will also require more attention and effort to make a release.

This will potentially make it easier for other contributors to land code in LTS staging, and I for one would enjoy seeing that job more distributed.

I think there are a variety of other pros and cons, but to making it easier for others to participate in the LTS process wins out.

Thoughts?

TLDR;

When a commit is approved for LTS it will immediately be landed on v4.x-staging

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions