From a5cc2896d7da7c4f47f377bfd204034a3f87a194 Mon Sep 17 00:00:00 2001
From: Anderson Grudtner Martins <anderson@publishpress.com>
Date: Tue, 5 May 2020 15:50:49 -0300
Subject: [PATCH] Add issue templates for Github

---
 .github/ISSUE_TEMPLATE/bug_report.md          | 49 +++++++++++++++++++
 .github/ISSUE_TEMPLATE/feature_request.md     | 20 ++++++++
 .github/ISSUE_TEMPLATE/release-free-plugin.md | 35 +++++++++++++
 .github/ISSUE_TEMPLATE/release-pro-plugin.md  | 27 ++++++++++
 4 files changed, 131 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/bug_report.md
 create mode 100644 .github/ISSUE_TEMPLATE/feature_request.md
 create mode 100644 .github/ISSUE_TEMPLATE/release-free-plugin.md
 create mode 100644 .github/ISSUE_TEMPLATE/release-pro-plugin.md

diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
new file mode 100644
index 00000000..6c978fdb
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -0,0 +1,49 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+Your issue may already be reported!
+Please search on the [issue track](../) before creating one.
+
+## Expected Behavior
+
+<!--- If you're describing a bug, tell us what should happen -->
+<!--- If you're suggesting a change/improvement, tell us how it should work -->
+
+## Current Behavior
+
+<!--- If describing a bug, tell us what happens instead of the expected behavior -->
+<!--- If suggesting a change/improvement, explain the difference from current behavior -->
+
+## Possible Solution
+
+<!--- Not obligatory, but suggest a fix/reason for the bug, -->
+<!--- or ideas how to implement the addition or change -->
+
+## Steps to Reproduce (for bugs)
+
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+
+<!--- How has this issue affected you? What are you trying to accomplish? -->
+<!--- Providing context helps us come up with a solution that is most useful in the real world -->
+
+## Your Environment
+
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+
+* Version used:
+* Browser Name and version:
+* Operating System and version (desktop or mobile):
+* Link to your project:
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
new file mode 100644
index 00000000..bbcbbe7d
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
diff --git a/.github/ISSUE_TEMPLATE/release-free-plugin.md b/.github/ISSUE_TEMPLATE/release-free-plugin.md
new file mode 100644
index 00000000..44c15600
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/release-free-plugin.md
@@ -0,0 +1,35 @@
+---
+name: Release the Free version (team only)
+about: Describes default checklist for the plugin's release process.
+title: Release PublishPress Authors v[VERSION]
+labels: release
+assignees: ''
+
+---
+
+To release the Free plugin please make sure to check all the checkboxes below.
+
+### Pre-release Checklist
+
+- [ ] Run `composer update --no-dev` and check if there is any relevant update. Check if you need to lock the current version for any dependency.
+- [ ] Commit changes to the `development` branch
+- [ ] Update the changelog - make sure all the changes are there with a user-friendly description
+- [ ] Update the version number to the next stable version. Use `$ phing set-version`
+- [ ] Pull to the `development` branch
+- [ ] Build the zip using `$ phing build`
+- [ ] Send to the team for testing
+
+### Release Checklist
+
+- [ ] Create a Pull Request and merge it into the `master` branch
+- [ ] Create the Github release (make sure it is based on the `master` branch and correct tag)
+
+#### SVN Repo
+- [ ] Cleanup the `trunk` directory.
+- [ ] Unzip the built package and move files to the `trunk`
+- [ ] Remove any eventual file that shouldn't be released in the package (if you find anything, make sure to create an issue to fix the build script)
+- [ ] Look for new files `$ svn status | grep \?` and add them using `$ svn add <each_file_path>`
+- [ ] Look for removed files `$ svn status | grep !` and remove them `$ svn rm <each_file_path>`
+- [ ] Create the new tag `$ svn cp trunk tags/<version>`
+- [ ] Commit the changes `$ svn ci 'Releasing <version>'`
+- [ ] Wait until WordPress updates the version number and make the final test updating the plugin in a staging site
diff --git a/.github/ISSUE_TEMPLATE/release-pro-plugin.md b/.github/ISSUE_TEMPLATE/release-pro-plugin.md
new file mode 100644
index 00000000..2640dcf6
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/release-pro-plugin.md
@@ -0,0 +1,27 @@
+---
+name: Release the Pro version (team only)
+about: Describes default checklist for releasing the Pro plugin;
+title: Release PublishPress Authors Pro v[VERSION]
+labels: release
+assignees: ''
+
+---
+
+To release the Pro plugin please make sure to check all the checkboxes below.
+
+### Pre-release Checklist
+
+- [ ] Run `composer update --no-dev` and check if there is any relevant update. Check if you need to lock the current version for any dependency.
+- [ ] Commit changes to the `development` branch
+- [ ] Update the changelog - make sure all the changes are there with a user-friendly description
+- [ ] Update the version number to the next stable version. Use `$ phing set-version`
+- [ ] Pull to the `development` branch
+- [ ] Build the zip using `$ phing build`
+- [ ] Send to the team for testing
+
+### Release Checklist
+
+- [ ] Create a Pull Request and merge it into the `master` branch
+- [ ] Create the Github release (make sure it is based on the `master` branch and correct tag)
+- [ ] Update EDD registry and upload the new package
+- [ ] Make the final test updating the plugin in a staging site