Raw Notes from #wptybee Updates Session

gistfile1.html

<h1 id="updatesinyourface">Updates in your Face</h1>
<h2 id="farfuture">Far Future</h2>
<ul>
	<li>Make updates as smooth and magical and graceful as possible</li>
	<li>Continuous releases</li>
	<li>Move from shrinkwrap to more agile, continuous development</li>
	<li>Perhaps a direction, not a goal</li>
	<li>People hate change, and they hate change they didn’t opt in to</li>
	<li>Language pack Plugins, Core, Themes, in that order?</li>
</ul>
<h2 id="languagepacks">Language packs</h2>
<ul>
	<li>Auto update, daily</li>
	<li>Piggyback on other update routines</li>
	<li>Possible security concerns… XSS in a language pack</li>
</ul>
<h2 id="minorvsmajor">Minor vs Major</h2>
<ul>
	<li>Minor/security should always be updated to immediately</li>
</ul>
<h2 id="testupdatebeforeitgoeslive">Test update before it goes live</h2>
<ul>
	<li>Run it in the upgrade dir (wp-includes/wp-admin)</li>
	<li>User the main install as a “client” to test the tentative update version</li>
	<li>Test whitescreen of front page before upgrade is finalized</li>
</ul>
<h2 id="hurdles">Hurdles</h2>
<ul>
	<li>If we break something, we break trust</li>
	<li>Rollbacks in case the update can’t update a file, or if it whitescreens</li>
</ul>
<h2 id="actionables">Actionables</h2>
<ul>
	<li>Host recommendations</li>
	<li>
<ul>
	<li>User owns and executes files</li>
</ul>
</li>
	<li>
<ul>
	<li>Clearly communicate our requirements to hosts, and when they change</li>
</ul>
</li>
	<li>
<ul>
	<li>Don’t “grandfather” old versions of softwares indefinitely</li>
</ul>
</li>
	<li>MD5 verification</li>
	<li>Language packs auto update</li>
	<li>UPDATE ALL button (plugins, plugins + core) with punnett square</li>
	<li>Progress bar, JS update of counters</li>
	<li>Download things ahead of time</li>
	<li>Whitescreen testing before update is finalized</li>
	<li>Make updates more magical</li>
	<li>Jokey/Gamey strings on update process</li>
</ul>