Skip to content

Adapt branches and release automation for Parse Server 5 LTS (remove Parse Server 4 LTS) #8275

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
6 tasks done
Tracked by #8225
mtrezza opened this issue Nov 2, 2022 · 2 comments
Closed
6 tasks done
Tracked by #8225

Adapt branches and release automation for Parse Server 5 LTS (remove Parse Server 4 LTS) #8275

mtrezza opened this issue Nov 2, 2022 · 2 comments
Labels
block:major Needs to be resolved before next major release; remove label afterwards state:breaking Breaking change requires major version increment and `BREAKING CHANGE` commit message type:feature New feature or improvement of existing feature

Comments

@mtrezza
Copy link
Member

mtrezza commented Nov 2, 2022 •
edited
Loading

New Feature / Enhancement Checklist

Current Limitation

With release of Parse Server 6.

  • Parse Server 4 LTS branched will be archived (no future commits)
  • Parse Server 5 branch moves to LTS

Feature / Enhancement Description

  • Create LTS branch release-5.x.x
  • Update CI on branch release-5.x.x for LTS
  • Lock branch release-4.x.x via branch protection rule; no further commits allowed

In addition made changes so that future LTS branches won't require manual code changes and can follow the simplified process described in Publishing Major Release (Yearly Release):

Example Use Case

n/a

Alternatives / Workarounds

n/a
@parse-github-assistant
Copy link

parse-github-assistant bot commented Nov 2, 2022 •
edited
Loading

Thanks for opening this issue!

  • 🎉 We are excited about your ideas for improvement!

@mtrezza mtrezza mentioned this issue Nov 2, 2022
Closed
31 tasks
@mtrezza mtrezza added block:major Needs to be resolved before next major release; remove label afterwards state:breaking Breaking change requires major version increment and `BREAKING CHANGE` commit message type:feature New feature or improvement of existing feature labels Nov 2, 2022
@mtrezza
Copy link
Member Author

mtrezza commented Nov 19, 2022

Closing, all tasks done (see above)

@mtrezza mtrezza closed this as completed Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
block:major Needs to be resolved before next major release; remove label afterwards state:breaking Breaking change requires major version increment and `BREAKING CHANGE` commit message type:feature New feature or improvement of existing feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mtrezza