-
Notifications
You must be signed in to change notification settings - Fork 19
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.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prep for 1.0.0 release #34
Conversation
Resolves #4. |
@todo confirm libraries to include
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great!
@adamsilverstein made those changes, plus applied the description/license updates in other areas across the plugin. Likely some merge conflicts we need to review later with the plugin renaming changes, will worry about that post-summit. |
@johnwatkins0 yep, I think you're right that #21 is covered here, thanks! I'll let @adamsilverstein determine if anything else is needed on this PR, as he'll run the release as 1.0.0 is deemed ready. |
Resolves #21. |
Also, resolves #32 |
# Conflicts: # autotweet.php # readme.txt
Also fixes #18 |
PR for tracking changes for the 1.0.0 release. Target release date: TBD
Fixes: #21
Release steps
develop
, cut a release branch namedrelease/1.0.0
for your changes.autotweet.php
if it does not already reflect the version being released.CHANGELOG.md
andreadme.txt
.pot
file by runningnpm run makepot
..github/action-release/rsync-filter.txt
.Leaving steps below for a follow up PR to do the actual release:
develop
, then do the same fordevelop
intomaster
.master
contains the stable development version.master
branch to GitHub, e.g.git push origin master
.stable
branch and test for functionality locally.1.0.0
on thestable
branch in GitHub. It should now appear under releases and in the WordPress admin as an update as well.Due date (optional)
field) and link to GitHub release (in theDescription
field), then close1.0.0
milestone1.0.0
do not make it into the release, update their milestone to1.1.0
orFuture Release