Embed Size (px)
DESCRIPTION
A presentation of sane practices for deploying plugin updates.
Citation preview
Updates are important
new features, bug fixes, security updates
Story time
Beta testconsider beta releases for large updates
Announce betassend out email announcements
write blog posts
write clear upgrade instructions
stress the importance of staging servers
give a list of expectations
Multiple betasrelease beta 1
fix bugs over next week
release beta 2
fix more bugs over next week
repeat until stable
Tag releases
Using gitgit tag 1.5
git push origin 1.5
Using svnsvn cp trunk tags/1.5
svn ci -m “Uploading version 1.5”
Change logsmake detailed, clear change logs
changes logs are for both developers and users
Badmade cool improvements
fixed some gnarly bugs
GoodFix: pass $item_amount through round() in PayPal
Fix: added missing text domain to strings in account.php
New: added new Heartbeat API integration for sale stats
Badcool stuff for 1.5
GoodAdded new “mp_query_args” filter to main posts
queryDeprecated mp_do_this(), use mp_do_that()
instead
Track issuesfeature and bug tracking
it’s everything that leads up to a release
Release oftendo not be afraid to push out a new update, if
needed
bugs happen and users prefer an update to a bug
Use a deploy scriptfor plugins hosted on WordPress.org and Github,
use a script to deploy to WordPress.org from Github
Some optionsMark Jaquith’s: http://goo.gl/V5A6Db
Paul Clark’s (forked from Mark’s): http://goo.gl/idDuJe
Include auto updaters
commercial plugins should always have an automatic update system to make it easier for
customers
neglecting it is a disservice and security risk
Some optionsEDD Software Licensing: http://goo.gl/Zo6xmW
Github plugin updater: http://goo.gl/vXTMS2
WP Updates: http://wp-updates.com/
Thanks@pippinsplugins
