Skip to content
This repository was archived by the owner on Feb 22, 2023. It is now read-only.

[none] Add release process to CONTRIBUTING.md #2304

Merged
merged 2 commits into from
Nov 25, 2019
Merged

[none] Add release process to CONTRIBUTING.md #2304

merged 2 commits into from
Nov 25, 2019

Conversation

mklim
Copy link
Contributor

@mklim mklim commented Nov 25, 2019

Description

This provides information on how to publish plugins going forward with
the new flutter_plugin_tools publish-plugin command.

In addition to that this documents our general process, which is a
general team health issue we've been wanting for awhile.

Related Issues

DO NOT MERGE until flutter/plugin_tools#65 is published.
Related to flutter/flutter#42934.
Helps some points in flutter/flutter#27258.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

  • I read the Contributor Guide and followed the process outlined there for submitting PRs.
  • My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
  • All existing and new tests are passing.
  • I updated/added relevant documentation (doc comments with ///).
  • The analyzer (flutter analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
  • I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
  • I updated CHANGELOG.md to add a description of the change.
  • I signed the CLA.
  • I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

  • Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
  • No, this is not a breaking change.

This provides information on how to publish plugins going forward with
the new `flutter_plugin_tools publish-plugin` command.

In addition to that this documents our general process, which is a
general team health issue we've been wanting for awhile.

DO NOT MERGE until `flutter_plugin_tools publish-plugin` has been merged
and released.
@mklim mklim marked this pull request as ready for review November 25, 2019 22:38
Note that the flutter_plugin_tools command is new, and add some
information on how to release manually if needed.
@mklim mklim merged commit 8eca031 into flutter:master Nov 25, 2019
@mklim mklim deleted the release_readme_update branch November 25, 2019 23:26
sungmin-park pushed a commit to sungmin-park/flutter-plugins that referenced this pull request Dec 17, 2019
This provides information on how to publish plugins going forward with
the new `flutter_plugin_tools publish-plugin` command.

In addition to that this documents our general process, which is a
general team health issue we've been wanting to fix for awhile.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants