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.

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

Merged
merged 36 commits into from
Oct 16, 2019
Merged

Prep for 1.0.0 release #34

merged 36 commits into from
Oct 16, 2019

Conversation

jeffpaul
Copy link
Member

@jeffpaul jeffpaul commented Aug 23, 2019

PR for tracking changes for the 1.0.0 release. Target release date: TBD

Fixes: #21

Release steps

  • Starting from develop, cut a release branch named release/1.0.0 for your changes.
  • Version bump: Bump the version number in autotweet.php if it does not already reflect the version being released.
  • Changelog: Add/update the changelog in CHANGELOG.md and readme.txt
  • Update the .pot file by running npm run makepot.
  • Check to be sure any new files/paths that are unnecessary in the production version are included in .github/action-release/rsync-filter.txt.

Leaving steps below for a follow up PR to do the actual release:

  • Merge: Make a non-fast-forward merge from your release branch to develop, then do the same for develop into master. master contains the stable development version.
  • Push: Push your master branch to GitHub, e.g. git push origin master.
  • Wait for build: Head to the Actions tab in the repo and wait for it to finish if it hasn't already. If it doesn't succeed, figure out why and start over.
  • Check the build: Check out the stable branch and test for functionality locally.
  • Git tag: Create the release as 1.0.0 on the stable branch in GitHub. It should now appear under releases and in the WordPress admin as an update as well.
  • Edit the 1.0.0 milestone with release date (in the Due date (optional) field) and link to GitHub release (in the Description field), then close 1.0.0 milestone
  • If any open issues or PRs which were milestoned for 1.0.0 do not make it into the release, update their milestone to 1.1.0 or Future Release

@jeffpaul jeffpaul added this to the 1.0.0 milestone Aug 23, 2019
@jeffpaul jeffpaul self-assigned this Aug 23, 2019
@jeffpaul
Copy link
Member Author

Resolves #4.

@jeffpaul
Copy link
Member Author

jeffpaul commented Aug 23, 2019

  • add readme.md, porting from readme.txt
  • add license.md
  • add changelog to readme.txt
  • add libraries to credits.md
  • add v0.1.0 link to changelog.md
  • confirm contributors in credits.md

tenup-auto-tweet.php Outdated Show resolved Hide resolved
readme.txt Show resolved Hide resolved
Copy link

@adamsilverstein adamsilverstein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great!

README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
@jeffpaul
Copy link
Member Author

@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
Copy link
Member

@jeffpaul Would this resolve #21 ? I was about to start typing up something on post type support, but it looks like the note in this README.md overview has it pretty much covered.

Is there anything I can do to help with this PR?

@jeffpaul
Copy link
Member Author

jeffpaul commented Oct 8, 2019

@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.

@jeffpaul
Copy link
Member Author

jeffpaul commented Oct 8, 2019

Resolves #21.

@adamsilverstein
Copy link

Also, resolves #32

@adamsilverstein
Copy link

Also fixes #18

@adamsilverstein adamsilverstein changed the title Release version 1.0.0 Prep for 1.0.0 release Oct 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

document post_type_supports requirement [1 hr.]
3 participants