Difference between revisions of "User:Torley Linden/New release checklist"
Jump to navigation
Jump to search
| Line 7: | Line 7: | ||
* Open up ''all'' resolved issues in Firefox [http://torley.com/why-my-web-browsers-vertical-tabs-rock-hardcore vertical tabs]. Macro-izing helps. If there are many, break it down into 2 or 3 passes. | * Open up ''all'' resolved issues in Firefox [http://torley.com/why-my-web-browsers-vertical-tabs-rock-hardcore vertical tabs]. Macro-izing helps. If there are many, break it down into 2 or 3 passes. | ||
* For each issue: | * For each issue: | ||
** Reopen it if it was "Fixed Internally". | ** Reopen it if it was "Fixed Internally" (deprecated). Else, "Resolve (Fix Pending)". | ||
** Close it as "Fixed", set "Fix version/s" to the one in the blog post ([http://jira.secondlife.com/secure/project/ManageVersions.jspa?pid=10003 create one] if it doesn't exist yet), and set the "Assignee" to the correct Linden (match the internal issue). If you don't know/can't find their Linden name, set it to "WorkingOnIt Linden". | ** Close it as "Fixed", set "Fix version/s" to the one in the blog post ([http://jira.secondlife.com/secure/project/ManageVersions.jspa?pid=10003 create one] if it doesn't exist yet), and set the "Assignee" to the correct Linden (match the internal issue). If you don't know/can't find their Linden name, set it to "WorkingOnIt Linden". | ||
** Copy-and-paste a friendly message communicating resolution. ''Make sure'' it links to the blog post ''AND'' states which version an issue was fixed in. Both of these are highly recommended for reducing ambiguity, e.g., complaints of "Hey it's not fixed yet!" For example: | ** Copy-and-paste a friendly message communicating resolution. ''Make sure'' it links to the blog post ''AND'' states which version an issue was fixed in. Both of these are highly recommended for reducing ambiguity, e.g., complaints of "Hey it's not fixed yet!" For example: | ||
Revision as of 10:16, 31 December 2007
Hey Torley, I'm you. Here's what you need to do.
(The following applies to main viewer and WindLight releases, and sometimes Havok4 Beta, but not RC viewers, etc.)
General
- Go to the Official Linden Blog and find the appropriate new release post.
- Open up all resolved issues in Firefox vertical tabs. Macro-izing helps. If there are many, break it down into 2 or 3 passes.
- For each issue:
- Reopen it if it was "Fixed Internally" (deprecated). Else, "Resolve (Fix Pending)".
- Close it as "Fixed", set "Fix version/s" to the one in the blog post (create one if it doesn't exist yet), and set the "Assignee" to the correct Linden (match the internal issue). If you don't know/can't find their Linden name, set it to "WorkingOnIt Linden".
- Copy-and-paste a friendly message communicating resolution. Make sure it links to the blog post AND states which version an issue was fixed in. Both of these are highly recommended for reducing ambiguity, e.g., complaints of "Hey it's not fixed yet!" For example:
- Thanx again for your reports and helping us to make progress! This bug is fixed in the newest WindLight version -- Second Life 1.18.5 (74965). Download link and more info here:
- Keep watching the Official Linden Blog and check out http://wiki.secondlife.com/wiki/Windlight for continued WindLight updates!
- If an issue requires any specific, non-cookie-cutter notes, share 'em. Always, always thank Resis for reporting and providing details which aided in an issue's fix0ring.
- After done with an issue, move to the next tab (Ctrl-Page Down) and repeat the above steps.
- When all done a batch, right-click a tab and select "Close Other Tabs" to "fold the deck".
WindLight
- Copy URL of Pastrami Linden's update blog post to the WindLight info-page.
- Update WindLight FAQ as necessary.