A presentation of sane practices for deploying plugin updates.

1. Sane plugin updates
http://pippinsplugins.com
@pippinsplugins

2. Updates are important
new features, bug fixes, security updates

3. Story time

4. Beta test
consider beta releases for large updates

5. Announce betas
send out email announcements
write blog posts
write clear upgrade instructions
stress the importance of staging servers
give a list of expectations

6. Multiple betas
release beta 1
fix bugs over next week
release beta 2
fix more bugs over next week
repeat until stable

7. Tag releases

8. Using git
git tag 1.5
git push origin 1.5

9. Using svn
svn cp trunk tags/1.5
svn ci -m “Uploading version 1.5”

10. Change logs
make detailed, clear change logs
changes logs are for both developers and users

11. Bad
made cool improvements
fixed some gnarly bugs

12. Good
Fix: 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

13. Bad
cool stuff for 1.5

14. Good
Added new “mp_query_args” filter to main posts query
Deprecated mp_do_this(), use mp_do_that() instead

15. Track issues
feature and bug tracking
it’s everything that leads up to a release

16. Release often
do not be afraid to push out a new update, if needed
bugs happen and users prefer an update to a bug

17. Use a deploy script
for plugins hosted on WordPress.org and Github, use a
script to deploy to WordPress.org from Github

18. Some options
Mark Jaquith’s: http://goo.gl/V5A6Db
Paul Clark’s (forked from Mark’s): http://goo.gl/idDuJe

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

20. Some options
EDD Software Licensing: http://goo.gl/Zo6xmW
Github plugin updater: http://goo.gl/vXTMS2
WP Updates: http://wp-updates.com/

21. Thanks
@pippinsplugins