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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

馃彈 Update Cherry-pick template with new release names #26542

Merged
merged 7 commits into from Jan 29, 2020
Merged

馃彈 Update Cherry-pick template with new release names #26542

Changes from 3 commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
477e08f
馃彈 Update Cherry-pick template with new release names
rsimha Jan 29, 2020
e8a3e37
Remove duplicate fronttext
rsimha Jan 29, 2020
066b249
Remove blank line
rsimha Jan 29, 2020
a2933d5
Include LTS
rsimha Jan 29, 2020
8295d9f
Fix incorrect link to cherry-pick documentation
rsimha Jan 29, 2020
e6064f0
Fix template name
rsimha Jan 29, 2020
94c7b2f
Format label names
rsimha Jan 29, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
19 changes: 11 additions & 8 deletions .github/ISSUE_TEMPLATE/cherry_pick_template.md
View file
Open in desktop
Expand Up @@ -2,24 +2,27 @@
name: Cherry-pick template
about: Used to request a cherry-pick. See go.amp.dev/cherry-picks
title: "\U0001F338 Cherry-pick request for #<ISSUE_NUMBER> into #<RELEASE_ISSUE> (Pending)"
labels: 'Type: Release'
labels: 'Cherry Pick: Beta, Cherry Pick: Experimental, Cherry Pick: Stable, Type:
Release'
assignees: ''
---

<!--
MUST: Replace *everything* in angle brackets in the title AND body of this issue.
MUST: Update issue labels to indicate which channels the cherry-pick is going into.

If you have any questions see the [cherry-pick documentation](https://github.com/ampproject/amphtml/blob/master/contributing/release-schedule.md#cherry-picks).
-->

# Cherry-pick request

<!--
TIP: Cherry-picks into production most likely require a cherry-pick into RC too. Otherwise, your fix will be lost when the RC is promoted.
TIP: Cherry-picks into Stable most likely require a cherry-pick into Beta / Experimental too. Otherwise, your fix will be lost when Beta is promoted.
-->

| Issue | PR | Production? | RC? | [Release issue](https://github.com/ampproject/amphtml/labels/Type%3A%20Release) |
| :---------------: | :------------: | :----------: | :----------: | :-----------------------------------------------------------------------------: |
| #<_ISSUE_NUMBER_> | #<_PR_NUMBER_> | **<YES/NO>** | **<YES/NO>** | #<_RELEASE_ISSUE_> |
| Issue | PR | Stable? | Beta / Experimental? | [Release issue](https://github.com/ampproject/amphtml/labels/Type%3A%20Release) |
| :---------------: | :------------: | :----------: | :------------------: | :-----------------------------------------------------------------------------: |
| #<_ISSUE_NUMBER_> | #<_PR_NUMBER_> | **<YES/NO>** | **<YES/NO>** | #<_RELEASE_ISSUE_> |

## Why does this issue meet the [cherry-pick criteria](https://github.com/ampproject/amphtml/blob/master/contributing/release-schedule.md#cherry-pick-criteria)?

Expand All @@ -30,15 +33,15 @@ TIP: Be specific.
<_YOUR_REASONS_>

<!--
CONDITION: Cherry-picking into production but _not_ RC. Otherwise, delete.
CONDITION: Cherry-picking into Stable but _not_ Beta / Experimental. Otherwise, delete.
-->

## Why is a RC cherry-pick not needed?
## Why is a Beta / Experimental cherry-pick not needed?

<_YOUR_REASONS_>

<!--
MUST: Filling out the mini-PM template is required _after_ the deployment of a production cherry-pick. If this cherry-pick does not include production, the mini-PM section can be deleted.
MUST: Filling out the mini-PM template is required _after_ the deployment of a stable cherry-pick. If this cherry-pick does not include stable, the mini-PM section can be deleted.

MUST: This issue cannot be closed until the mini-PM is written and its action items are completed.
-->
Expand Down