Skip to content
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.

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

docs: Release procedure documentation #1649

Merged
merged 9 commits into from
May 27, 2022
Merged

Conversation

spydon
Copy link
Member

@spydon spydon commented May 22, 2022

Description

Just adds documentation about the release procedure and breaking changes.

Checklist

  • The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
  • I have read the Contributor Guide and followed the process outlined for submitting PRs.
  • I have updated/added tests for ALL new/updated/fixed functionality.
  • I have updated/added relevant documentation in docs and added dartdoc comments with ///.
  • I have updated/added relevant examples in examples.

Breaking Change

  • No, this is not a breaking change.

CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
Copy link
Member

@erickzanardo erickzanardo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent! LGTM!

CONTRIBUTING.md Outdated Show resolved Hide resolved
Copy link
Contributor

@wolfenrain wolfenrain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left a few comments that I atleast want some clarity on, LGTM apart from that tho

CONTRIBUTING.md Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated
- Search through the codebase for `@Deprecated` methods/fields and remove the ones that are marked
for removal in the version that you are intending to release.
- Create a PR containing the changes for removing the deprecated entities.
- Run `melos version -V <package>:<version> -V <package>:<version>` for Melos to generate a
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Twice the -V? Is it meant to be current vs next? If so we we should make that more explicit in the command

Copy link
Member Author

@spydon spydon May 27, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Twice the -V?

Yes, once for each package, and the version is the version for that package. Would it be more clear if I wrote it like this?

Suggested change
- Run `melos version -V <package>:<version> -V <package>:<version>` for Melos to generate a
- Run `melos version -V <package1>:<version> -V <package2>:<version>` for Melos to generate a

spydon and others added 3 commits May 27, 2022 14:32
Co-authored-by: Jochum van der Ploeg <jochum.vanderploeg@verygood.ventures>
Copy link
Contributor

@wolfenrain wolfenrain left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, one small nit

CONTRIBUTING.md Outdated Show resolved Hide resolved
CONTRIBUTING.md Outdated Show resolved Hide resolved
@spydon spydon enabled auto-merge (squash) May 27, 2022 13:08
@spydon spydon merged commit 73b7a4f into main May 27, 2022
@spydon spydon deleted the spydon.add-release-procedure-docs branch May 27, 2022 13:14
st-pasha pushed a commit to st-pasha/flame that referenced this pull request May 29, 2022
Adds documentation about the release procedure and breaking changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants