-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #565 from publishpress/feature/release-2.9.1
Feature/release 2.9.1
- Loading branch information
Showing
23 changed files
with
2,607 additions
and
2,282 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
--- | ||
name: Bug report | ||
about: Create a report to help us improve | ||
title: '' | ||
labels: 'bug' | ||
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: |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
--- | ||
name: Feature request | ||
about: Suggest an idea for this project | ||
title: '' | ||
labels: 'enhancement' | ||
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. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
--- | ||
name: Release the Free version (team only) | ||
about: Describes default checklist for the plugin's release process. | ||
title: Release v[VERSION] | ||
labels: release | ||
assignees: '' | ||
|
||
--- | ||
|
||
To release the Free plugin please make sure to check all the checkboxes below. | ||
|
||
### Pre-release Checklist | ||
|
||
- [ ] Create the release branch as `release-<version>` based on the development branch | ||
- [ ] Make sure to directly merge or use Pull Requests to merge hotfixes or features branches into the release branch | ||
- [ ] Run `composer update` and check if there is any relevant update. Check if you need to lock the current version for any dependency. The `--no-dev` argument is optional here, since the build script will make sure to run the build with that argument. | ||
- [ ] Update the changelog - make sure all the changes are there with a user-friendly description and that the release date is correct | ||
- [ ] Update the version number to the next stable version. Use `$ vendor/bin/robo version <version-number>` | ||
- [ ] Commit the changes to the release branch | ||
- [ ] Build the zip package using `$ vendor/bin/robo build`. It should create a package in the `./dist` dir. | ||
- [ ] Send to the team for testing | ||
|
||
### Release Checklist | ||
|
||
- [ ] Create a Pull Request and merge the release branch it into the `master` branch | ||
- [ ] Merge the `master` branch into the `development` 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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
--- | ||
name: Release the Pro version (team only) | ||
about: Describes default checklist for releasing the Pro plugin; | ||
title: Release Pro v[VERSION] | ||
labels: release | ||
assignees: '' | ||
|
||
--- | ||
|
||
To release the Pro plugin please make sure to check all the checkboxes below. | ||
|
||
### Pre-release Checklist | ||
|
||
- [ ] Create the release branch as `release-<version>` based on the development branch | ||
- [ ] Make sure to directly merge or use Pull Requests to merge hotfixes or features branches into the release branch | ||
- [ ] Clone free version shared file to pro version | ||
- [ ] Run `composer update` and check if there is any relevant update. Check if you need to lock the current version for any dependency. The `--no-dev` argument is optional here, since the build script will make sure to run the build with that argument. | ||
- [ ] Update the changelog - make sure all the changes are there with a user-friendly description and that the release date is correct | ||
- [ ] Update the version number to the next stable version. Use `$ vendor/bin/robo version <version-number>` | ||
- [ ] Commit the changes to the release branch | ||
- [ ] Build the zip package using `$ vendor/bin/robo build`. It should create a package in the `./dist` dir. | ||
- [ ] Send to the team for testing | ||
|
||
### Release Checklist | ||
|
||
- [ ] Create a Pull Request and merge the release branch it into the `master` branch | ||
- [ ] Merge the `master` branch into the `development` 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 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.