Jetpack/Release Process: Difference between revisions

Jump to navigation Jump to search
Line 191: Line 191:


In the bug you filed earlier about pushing the website changes to production, comment that now is the time to do the work and wait for its assignee to do it.
In the bug you filed earlier about pushing the website changes to production, comment that now is the time to do the work and wait for its assignee to do it.
== Update Blog ==
The [http://mozillalabs.com/jetpack/ Jetpack blog] lives at mozillalabs.com/jetpack. Its content (by which I mean the content that surrounds the blog posts, i.e. logos, navigation links, etc.) is release-neutral, so it generally doesn't need changing.
If that ever changes, then it will need to be updated. Since there is no way to stage changes to the blog, this will here in the Release step rather than in the Prepare to Release step.
{{note|changes to the blog can take several hours to show up on the site because of server-side caching. To check that your changes have been applied, add "?[some unique string]" to the end of the URL, which bypasses the cache.}}


== Publish Blog Post ==
== Publish Blog Post ==


Access the blog's Wordpress admin page and go to Posts. Publish the post you previously wrote.
Access the Add-ons blog's Wordpress admin page and go to Posts. Publish the post you previously drafted.


{{note|changes to the blog can take several hours to show up on the site because of server-side caching. To check that the post has been published, add "?[some unique string]" to the end of the URL, which bypasses the cache.}}
{{note|changes to the blog can take several hours to show up on the site because of server-side caching. To check that the post has been published, add "?[some unique string]" to the end of the URL, which bypasses the cache.}}
canmove, Confirmed users
2,056

edits

Navigation menu