create a change policy for package:dart_flutter_team_lints (#278)

* create a change policy for package:dart_flutter_team_lints

* update the changelog

* Update CHANGELOG.md

- fix typo

* Update pkgs/dart_flutter_team_lints/README.md

Co-authored-by: Kevin Moore <kevmoo@users.noreply.github.com>

---------

Co-authored-by: Kevin Moore <kevmoo@users.noreply.github.com>

pkgs/dart_flutter_team_lints/CHANGELOG.md

@@ -1,3 +1,7 @@
+## 3.1.1-wip
+
+- Contribute a (brief) change policy to the readme.
+
 ## 3.1.0
 
 - Added `unnecessary_library_name`.

pkgs/dart_flutter_team_lints/README.md

@@ -28,3 +28,19 @@ then, add an `analysis_options.yaml` file to your project:
 ```yaml
 include: package:dart_flutter_team_lints/analysis_options.yaml
 ```
+
+## Suggesting changes to the lint set
+
+In order to suggest a change to the `package:dart_flutter_team_lints` lint set,
+please [file an issue](https://github.com/dart-lang/ecosystem/issues/new?template=dart_flutter_team_lints.md)
+against the package. A representative group of Dart and Flutter team members,
+along with interested parties, will then discuss the lint addition or removal.
+
+Changes to the lint set may be batched up in order to minimize churn for
+downstream codebases.
+
+Lint additions may go out in new package major versions. `package:lints` only
+ships lint additions in major versions as new lints are effectively breaking
+changes for repo CI systems. The packages downstream from this lint set are
+more scoped and better known however, so we have more room for flexibility for 
+changes to `package:dart_flutter_team_lints`.

pkgs/dart_flutter_team_lints/pubspec.yaml

@@ -1,6 +1,6 @@
 name: dart_flutter_team_lints
 description: An analysis rule set used by the Dart and Flutter teams.
-version: 3.1.0
+version: 3.1.1-wip
 repository: https://github.com/dart-lang/ecosystem/tree/main/pkgs/dart_flutter_team_lints
 
 environment: