Unverified Commit eea12df3 authored by Casey Hillers's avatar Casey Hillers Committed by GitHub

Update CP template to include timeline and changelog (#127507)

Based on recent feedback. Give more information in the CP template.
parent 7b67aa58
...@@ -6,6 +6,17 @@ assignees: ...@@ -6,6 +6,17 @@ assignees:
- itsjustkevin - itsjustkevin
- caseyhillers - caseyhillers
body: body:
- type: markdown
attributes:
value: |
<!---
Flutter releases generally follow the given timeline:
1. On Tuesday at 10 AM PT the CP list will be finalized for the week's release
A. If there's any stable CPs, a stable release will be shipped.
B. Based on discretion of the release team, a beta hotfix may be shipped.
2. Tuesday the release engineer for the week will get the release prepped
3. Wednesday morning at 10 AM PT the release will be shipped
-->
- type: input - type: input
id: issue_link id: issue_link
attributes: attributes:
...@@ -39,6 +50,15 @@ body: ...@@ -39,6 +50,15 @@ body:
The current branches can be found under release-caniddate-branch.version for [beta](https://github.com/flutter/flutter/blob/beta/bin/internal/release-candidate-branch.version) and [stable](https://github.com/flutter/flutter/blob/stable/bin/internal/release-candidate-branch.version) The current branches can be found under release-caniddate-branch.version for [beta](https://github.com/flutter/flutter/blob/beta/bin/internal/release-candidate-branch.version) and [stable](https://github.com/flutter/flutter/blob/stable/bin/internal/release-candidate-branch.version)
validations: validations:
required: true required: true
- type: textarea
id: changelog_description
attributes:
label: Changelog Description
description: >-
Explain this CP in one line that is accessible to most Flutter developers
See https://github.com/flutter/flutter/wiki/Hotfix-Documentation-Best-Practices for examples
validations:
required: true
- type: input - type: input
id: impacted_users id: impacted_users
attributes: attributes:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment