nyuuzyou/wikis huggingface dataset:
Glitch

A glitch is a programming error or quirk in software, usually originated from bad code to unused space in RAM. Glitches range from harmless to harmful, depending on what it effects. Glitches that are usually harmless could be beneficial to the player such as granting them extra lives or an "unlimited" amount of an item, etc. while harmful glitches could effect major parts of a game's code, rendering the game un-playable. 
Category:Technical Information
Missing Death Animation Glitch

The Missing death animation glitch is a bug present in the PSX version of Gex 3: Deep Cover Gecko. After the player makes it through the sewers part of Funky Town's map, they are greeted with two enemies that are placed in front of other interactive objects. When the player destroys the enemies, they are automatically destroyed and don't play the death animation giving to them. It is currently unknown why this happens, but a theory states that it could be because the other breakable objects may effect the enemy's animation, and prevents the animations from playing. While there are more of the same enemies later on in the map, they don't suffer from this glitch at all and play the proper death animation.
Category:Gex 3:Deep Cover Gecko Glitches
Category:PSX/Playstation 1 Glitches
Category:Minor Glitches
Missingno.

Missingno.is a glitch that occurs in the 1st Gen Pokemon games. The name stands for "Missing number" and was used as place holder data while the developers were working on the game. Since the game boy allows for 255 slots to be used for Pokemon data, and since only 151 "real" creatures were programmed in, players using various cheats can encounter this glitch due to empty unused slots. This also helps prevent other glitches to occur in game. It's harmless, but is often mistaken to be harmful to the player's game, however it is known to corrupt the player's hall of fame data which scrambles the part of the game that stores this data, by filling it with random bytes that usually originate from other previous events such as Pokemon encounters. Normal gameplay can continue, this glitch is also known to duplicate the player's 6th item which can be very beneficial to the player. Minor VRAM glitches also occur when the player attempts to view it's stats, but can be fixed by viewing the stats of a "real" Pokemon.
==Different Forms==
Missingno. come in different forms depending on the version and language of the game. The most common one is in the shape of a "L" with random pixels. Some different regions and versions of these games may crash while encountering Missingno., to bypass the crash it's recommended that the player encounter the fossil or ghost type Missingno. As these are valid sprite data in the game, these variations never effect the gameplay in any version or region.
==How To Encounter The Glitch==
If the player is playing Blue or Red, they may encounter Missingno. by use of the Old Man Trick or the Mew Trick. However in order for Missingno. to occur while using the Old Man Trick, the player must have specific letters or characters in certain parts of their name. (Note: A list of the proper letters and characters in the correct slots can be found on the Old Man Trick page.)
Category:Harmless Glitches
Category:Beneficial Glitches
Old Man Trick

The Old Man Trick is a glitch that occurs in Pokemon Blue and Red versions. It's the most commonly used method to encounter the glitch Pokemon, Missingno. Since the glitch was patched in Yellow version, a different method is used to encounter the glitch. The player must talk to the old man in Veridian City that teaches the player how to capture Pokemon. During the sequence, the player's name is temporarily changed to "OLD MAN" to show the proper text. However when this happens, after watching the sequence the player must then fly (or teleport) to Cinnabar Island and surf on the coast of Cinnabar. During this time, the player will encounter different Pokemon depending on the route the player was last in. The player will also encounter different glitched Pokemon depending on their name, in which if the player used the correct letters and characters in the proper slots they then will encounter Missingno. 
==How it Works==
When creating the map of which Pokémon appears where, the programmers made a mistake. The strip of land making up the Cinnabar Island Strait was programmed to be a place where wild Pokémon could appear, but they forgot to specify WHICH Pokémon could appear there! Whenever you enter a new area, the data for "What Pokémon appear where" is overwritten with the specific data for that area. However, because no data is specified for the Cinnabar Island Strait, the previous data will remain, enabling you to evidently catch Pokémon there from the last area you visited (this is what causes the Safari Zone trick to take place).
When you watch the Old Man's demonstration, the picture and text change from your name to "Old Man". For this to happen, the programmers changed the variables given to your name so the picture and text can show up as "Old Man". These are stored in the byte containing the data for "What Pokémon appear where" as this was the place the programmers would be a safe place to store them until the demonstration finishes, and they would be overwritten when you entered a new place anyway, but when you go directly from the Old Man's demonstration to the Cinnabar Island Strait, the data won't be overwritten as it should, leaving your name's variables in the "What Pokémon appear where" byte. None of these variable's HEX Values make sense, so it would fit that the Pokémon encountered there would not make sense. The game brings up an empty HEX Value so Missingno appears.
(Source: )
In order for the player to encounter Missingno., they must use the following letters in either the third, fifth, or seventh slot in their name. The characters the player should use to encounter "L" Missingno. are: Space,G,H,J,M,S,:,],a,b,c,m,o,p,v for the fossil and ghost type the player must have: w,x,y. (Note: Only characters the player may use without the need of a cheating device is listed, however there are other glitched characters the player can use by means of a cheating device to encounter Missingno.)
Category:Nintendo Game Boy Glitches
Category:Pokemon Glitches
Category:Harmless Glitches
Category: Beneficial Glitches
Category: Glitches Patched In Later Revisions
Spike Bug

The Spike Bug is a glitch that occurs in Sonic The Hedgehog for the Sega Mega Drive. If the player lands on spikes they will then lose all their rings and a life. (If they currently have a shield, that will be lost first, then their rings, and a life.) Many consider this a bug as the later Sonic games don't have this issue, and it was also addressed in Rev. 01 of the game. Since Sonic The Hedgehog is hacked excessively, one can fix the issue in a revision 00 ROM by means of a disassembly.
Category:Sega Mega Drive/Genesis Glitches
Category:Sonic the Hedgehog Glitches
Category:Minor Glitches
Category:Glitches Patched In Later Revisions
List of SUR station headcodes

Station name 	Headcode
Mount Baker 	MBK
Franklin High School	FHS
Jefferson Park 	JFP
4th Avenue 	4AV
Spokane Street 	SKS
1st Avenue 	1AV
CenturyLink Field 	CLF
King Street 	KST
Downtown 	DTN
Belltown 	BTN
Lower Queen Anne 	LQN
Queen Anne 	QNA
East Queen Anne 	EQA
Nickerson Street 	NKS
Fremont 	FMT
46th Street 	46S
Woodland Park 	WLP
Meridian 	MDN
Sheridan Beach (SUR)

Sheridan Beach station (SDB) was a former Metro station on the SUR Baker Line that was open from 1993 until 2005 when it was closed after the line was extended from Briarcrest to Edmonds. It served the neighbourhood of Sheridan Beach while it was in service.
Opened 	15 June 1993
Closed 	23 September 2005
Operator 	SUR
Passenger numbers (2004 - 05)	52,971
== History ==
The station was opened on 15 June 1993 as the new terminus station for the SUR's Baker Line Extension Phase I which was opened on the same day. The station had a relatively high ridership, averaging around 139,000 passengers in its first day of operation. The station had 1 island platform which could accommodate 4 trains due to its length. However, in later years, the station became used less and less, and its final blow came when the proposal for the line to be extended to Edmonds from Briarcrest was constructed. The station was officially closed on 23 September 2005 due to low ridership. Today, the station building still remains but is sealed off. The platform in the station remains intact and is occasionally used for tours and filming purposes.
SH

The Texas State Highway System, abbreviated as SH, is a system of roads funded and maintained by the State of Texas. Generally, their numbers range from 1 to 365, but there are some exceptions, such as (re-designated from ). There are two roads, and , that are part of this system but not of the number system. The first 26 SHs were designated as such in 1917. The others were designated in the 1920s and '30s, when suffixed SHs were removed or renumbered.
==List==
 (now ) (now , US 75, US 81) (now IH 40) (now US 70, US 183) (proposed) (former, see article) (now ) (former, see article)
Types

There are many types of numbered highways in Texas, roads maintained by the Texas Department of Transportation.
The biggest of these is the Interstate Highway System, on which this wiki does not usually focus because these are often outside of Texas.
Another is the United States Numbered Highway System, commonly known as US Highways, on which this wiki does not focus because, similar to Interstates, they run throughout the United States.
A third is the State Highway system (abbreviated as SH #), which includes major roads exclusively in Texas.
Contained within the SH system are their subtypes:
the State Highway Loop system (abbreviated as SL #), which includes looped roads in Texas,
the State Highway Spur system (abbreviated as SS #), which includes spur roads in Texas,
and the State Highway Beltway "system" (abbreviated as SB #), in which there is only one road: .
A fourth type is the x-to-Market Road system, of which there are too many subtypes to be described in brief.
Yet another type is the Park Road system (abbreviated as PR #), which appear in state and national parks.
A sixth is Recreational Roads (abbreviated as RE #), which serve "recognized recreational areas".
The final type is the Business road system, which is too weird and complicated to be described in brief.
That being said, excluding business, there are ten official "types" on this wiki: SH (State Highway), SL (State Highway Loop), SS (State Highway Spur), SB (State Highway Beltway), FM (Farm-to-Market), RM (Ranch-to-Market), RR (Ranch Road), UR (Urban Road), PR (Park Road), and RE (Recreational Road).
X-to-Market Road

x-to-market roads generally exist in rural areas. Generally, if the road is west of US 281, it is designated as a ranch to market road (abbreviated RM #), and if east of US 281 as a farm to market road (abbreviated FM #). Only one of these roads is designated as a ranch road (abbreviated RR #), which is at LBJ Ranch. In 1995, many x-to-Market Roads which were located in urban areas were redesignated as urban roads (abbreviated UR #). However, upon redesignation, the TxDOT did not change the shields, so urban roads are still shielded as RM or FM.
(WindRiver) Latest Results Report WindRiver

=Testing data=
 
 Test type: Full Pass Test
 Branch: master
 Milestone: 2.7 M2 RC2
 poky commit: be52da152a4d9f9e798844f592ec9ae7e051c658
 Autobuilder images repository: https://autobuilder.yocto.io/pub/releases/yocto-2.7_M2.rc2
 
=Summary Report=
	
=Detailed Report=
* 926de56da9469e3d4ea8349d8e7c9777ae6f93c1

< Back
{| class="wikitable"
|+Results
|- style="background-color:#F0F8FC; padding:10px;"
|Package Name ||Tests ran ||Passed ||Failed ||Passrate ||Last Passrate ||Run difference
|-
|ubuntu ||106 ||style="background-color:#C4FF33;" |105 ||style="background-color:#C4FF33;" |1 ||style="background-color:#C4FF33;"|99.0 ||style="background-color:#C4FF33;"|99.0 ||style="background-color:#C4FF33;"|No
|-
|ubuntu ||106 ||style="background-color:#C4FF33;" |105 ||style="background-color:#C4FF33;" |1 ||style="background-color:#C4FF33;"|99.0 ||style="background-color:#C4FF33;"|99.0 ||style="background-color:#C4FF33;"|No
* fcc67ae90feeceee204bdb36e45eacf8d056779a

< Back
{| class="wikitable"
|+Results
|- style="background-color:#F0F8FC; padding:10px;"
|Package Name ||Tests ran ||Passed ||Failed ||Passrate ||Last Passrate ||Run difference
|-
|ubuntu ||106 ||style="background-color:#C4FF33;" |105 ||style="background-color:#C4FF33;" |1 ||style="background-color:#C4FF33;"|99.0 ||style="background-color:#C4FF33;"|99.0 ||style="background-color:#C4FF33;"|No
|-
|opensuse ||106 ||style="background-color:#C4FF33;" |104 ||style="background-color:#C4FF33;" |2 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|No
|-
|fedora ||106 ||style="background-color:#C4FF33;" |105 ||style="background-color:#C4FF33;" |1 ||style="background-color:#C4FF33;"|99.0 ||style="background-color:#C4FF33;"|99.0 ||style="background-color:#C4FF33;"|No
|-
|centos ||106 ||style="background-color:#C4FF33;" |104 ||style="background-color:#C4FF33;" |2 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|98.0 ||style="background-color:#C4FF33;"|No
1.4 Features to Test Case

This page is work progress; the data displayed may not be correct/complete.
=1.5 Features that need to have TC's as soon as possible:=
=1.4 Features that need to have TC's as soon as possible:=
= 1.5 Features that need to be verified =
=The following 1.4 features ware selected by QA to have test cases made for them:=
=For the folowing 1.4 features QA will not make test cases:=
= 1.4 New Bugs:=
= 1.4 OPS Bugs:=
1.4 QA Runs

Weekly Test Report for Yocto 1.4 2013-03-21-2 Build https://wiki.yoctoproject.org/wiki/Weekly_Test_Report_for_Yocto_1.4_201303212_Build
Weekly Test Report for Yocto 1.4 2013-03-13-3 Build https://wiki.yoctoproject.org/wiki/Weekly_Test_Report_for_Yocto_1.4_201303133_Build
Full Pass Test Report for Yocto 1.3.1 RC2 2013-03-01-2 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.3.1_RC2_201303012_Build
Full Pass Test Report for Yocto 1.3.1 RC1 2013-02-26-2 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.3.1_RC1_201302262_Build
Full Pass Test Report for Yocto 1.4 M4 RC1 2013-02-20-2 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.4_M4_RC1_201302202_Build
Weekly Test Report for Yocto 1.4 2013-02-13 Build https://wiki.yoctoproject.org/wiki/Weekly_Test_Report_for_Yocto_1.4_20130213_Build
Full Pass Test Report for Yocto 1.4 M5 RC2 2013-03-27-1 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.4_M5_RC2_201303271_Build
Full Pass Test Report for Yocto 1.4 M5 RC3 2013-04-03-2 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.4_M5_RC3_201304032_Build
Full Pass Test Report for Yocto 1.4 M6 RC1 2013-04-11-3 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.4_M6_RC1_201304113_Build
Full Pass Test Report for Yocto 1.4 M6 RC2 2013-04-18-1 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.4_M6_RC2_201304181_Build
Full Pass Test Report for Yocto 1.4.1 RC1 2013-06-12-5 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.4.1_RC1_20130612-5_build
Full Pass Test Report for Yocto 1.4.2 RC2 2013-08-18 Build https://wiki.yoctoproject.org/wiki/Full_Pass_Test_Report_for_Yocto_1.4.2_RC1_2013-08-18_build
1.4 to be verified

== Resolved Bugs that need to be verified (1.4 M1,1.4 M2,1.4 M3,1.4 M4,1.4 M6,1.4 M6,1.4)==
== Features(enhancements) that need to be verified (1.4 M1,1.4 M2,1.4 M3,1.4 M4,1.4 M6,1.4 M6,1.4) ==
== Needinfo Bugs (1.4 M1,1.4 M2,1.4 M3,1.4 M4,1.4 M6,1.4 M6,1.4) ==
1.5 Distribution Tested

Here is the table with all the distributions covered by our test runs for 1.5.
 	Distro 	Ubuntu	Ubuntu	Ubuntu	Ubuntu	Fedora	Fedora	Fedora	OpenSuse	OpenSuse	CentOS
 	Build 	12.04 	12.10 	13.04 	13.10 	17 	18 	19 	12.3 	13.1 	6.4
M1	WW21 - 2013-05-21-1 - Weekly Yocto 1.5 M1 	X 	 	X 	N/A 	X 	X 	N/A 	X 	N/A 	X
M1	WW22 - 2013-05-28-2 - Fullpass Yocto 1.5 M1 	X 	X 	X 	N/A 	X 	X 	N/A 	X 	N/A 	X
M1	WW23 - 2013-06-04-5 - Fullpass Yocto 1.5_M1.RC1 	X 	X 	X 	N/A 	X 	X 	N/A 	X 	N/A 	X
M2	WW25 - 2013-06-18-2 - Weekly Yocto 1.5 M2 	X 	 	X 	N/A 	X 	X 	N/A 	X 	N/A 	X
M2	WW26 - 2013-06-25-2 - Weekly Yocto 1.5 M2 	X 	 	X 	N/A 	X 	X 	N/A 	X 	N/A 	X
M2	WW27 - 2013-07-03-3 - Full Pass Yocto 1.5_M2.RC1 	X 	X 	X 	N/A 	X 	X 	 	X 	N/A 	X
M2	WW28 - 2013-07-10-1 - Weekly Yocto 1.5 M2 	 	 	X 	N/A 	X 	X 	 	X 	N/A 	X
M3	WW29 - 2013-07-17-2 - Weekly Yocto 1.5 M3 	 	 	X 	N/A 	X 	X 	 	X 	N/A 	X
M3	WW30 - 2013-07-24-2 - Full Pass Yocto 1.5 M3 	X 	X 	X 	N/A 	X 	X 	 	X 	N/A 	X
M3	WW31 - 2013-07-31-1 - Full Pass Yocto 1.5_M3.rc1 	X 	X 	X 	N/A 	X 	X 	 	X 	N/A 	X
M4	WW33 - 2013-08-13-3 - Weekly Yocto 1.5 M4 	X 	 	X 	N/A 	X 	 	X 	X 	N/A 	X
M4	WW35 - 2013-08-28 - Full Pass Yocto 1.5 M4.rc2 	X 	 	X 	N/A 	X 	X 	X 	X 	N/A 	X
M4	WW36 - 2013-09-05 - Full Pass Yocto 1.5_M4.rc3 	X 	 	X 	N/A 	X 	X 	X 	X 	N/A 	X
M5	WW37 - 2013-09-11 - Full Pass Release Yocto 1.5 M5 rc1	 	 	X 	N/A 	X 	 	X 	X 	N/A 	X
reference:
* N/A - distribution not released yet
* X - tested distribution
* (blank) - skipped test on the distribution
1.5 QA owners

Here is the team owners for the 1.5 Yocto Project components:
Project Component Group	Component 	Owner
QEMU Machine 	qemuarm 	Huawei
QEMU Machine 	qemux86 	Huawei
QEMU Machine 	qemux86-64 	Huawei
QEMU Machine 	qemumips 	WindRiver
QEMU Machine 	qemuppc 	WindRiver
Core BSP 	atom-pc 	Intel
Core BSP 	beagleboard 	WindRiver
Core BSP 	mpc8315e-rdb 	WindRiver
Core BSP 	routerstationpro 	WindRiver
Target System 	Compliance Testing	WindRiver & Intel
Target System 	Stress Testing 	WindRiver & Intel
Target System 	System Performance	Intel
Developer Tools 	ADT 	WindRiver
Developer Tools 	Eclipse-plugin 	Intel
Developer Tools 	Build Appliance 	WindRiver
Build System 	Bitbake 	Intel
Build System 	HOB 	Intel
Build System 	Metadata 	WindRiver
Build System 	Build Performance 	Intel
1.5 QA run history meta-intel

=Yocto 1.5 meta-intel QA Run History=
== 1.5 M4 ==
WW35 - 2013-08-28 - meta-intel - Full Pass - 1.5_M4.rc2
WW36 - 2013-09-05 - meta-intel - FUll Pass - 1.5_M4.rc3
1.5 qa run history

=== Current Status ===
Here you can find the current testing status for the latest 1.5 Master branch
* 1.5 QA Status
* 1.5 Distribution Tested
=== 1.5 Runs ===
==== 1.5 M1 ====
Here are listed the 1.5_M1 QA runs
* WW21 - 2013-05-21-1 - Weekly Yocto 1.5 M1
* WW22 - 2013-05-28-2 - Fullpass Yocto 1.5 M1 
* WW23 - 2013-06-04-5 - Fullpass Yocto 1.5_M1.RC1
==== 1.5 M2 ====
Here are listed the 1.5_M2 QA runs 
* WW25 - 2013-06-18-2 - Weekly Yocto 1.5 M2
* WW26 - 2013-06-25-2 - Weekly Yocto 1.5 M2
* WW27 - 2013-07-03-3 - Full Pass Yocto 1.5_M2.RC1
* WW28 - 2013-07-10-1 - Weekly Yocto 1.5 M2 
==== 1.5 M3 ====
Here are listed the 1.5_M3 QA runs 
* WW29 - 2013-07-17-2 - Weekly Yocto 1.5 M3 
* WW30 - 2013-07-24-2 - Full Pass Yocto 1.5 M3
* WW31 - 2013-07-31-1 - Full Pass Yocto 1.5_M3.rc1
==== 1.5 M4 ====
Here are listed the 1.5_M4 QA runs
* WW33 - 2013-08-13-3 - Weekly Yocto 1.5 M4
* WW35 - 2013-08-28 - Full Pass Release 1.5_M4.rc2
* WW36 - 2013-09-05 - Full Pass Release 1.5_M4.rc3
==== 1.5 M5 ====
* WW37 - 2013-09-11 - Full Pass Release 1.5_M5.rc1
* WW38 - 2013-09-18 - Full Pass Release 1.5_M5.rc4
* WW39 - 2013-09-24 - Full Pass Release 1.5_M5.rc5
* WW41 - 2013-10-08 - Full Pass Release 1.5_M5.rc8
=== 1.5.1 Point release test runs ===
* WW50 - 2013-12-13 - Full Pass Release Dora 1.5.1 rc2
=== 1.5.2 Point release test runs ===
* WW18 - 2014-04-28 - Full Pass Release Dora 1.5.2 rc3
=== 1.5.3 Point release test runs ===
* WW28 - 2014-07-09 - Full Pass Release Dora 1.5.3
=== 1.5.4 Point release test runs ===
* WW48 - 2014-11-25 - Full Pass Release Dora 1.5.4
1.6 meta-intel qa run history

Here you can find the current testing status for the latest weekly 1.6 Master branch
* 1.6 QA Status - QA Live status report
=== 1.6 Runs ===
==== 1.6 M1 ====
WW49 - 2013-12-03 - meta-intel - Full Pass Release 1.6 M1.rc1
=== 1.6 M2 ===
WW03 - 2014-01-14 - meta-intel - Full Pass Release 1.6 M2.rc1
=== 1.6 M3 ===
WW08 - 2014-02-18 - meta-intel - Full Pass Release 1.6 M3.rc2
=== 1.6.1 ===
WW26 - 2014-06-23 - meta-intel full pass 1.6.1.rc3
1.6 qa owned bugs

= 1.6 QA Owned bugs =
List with all the bugs and features in Resolved state.
== 1.6 Features that need to be verified ==
== 1.6 Bugs that need to be verified owned by RO QA ==
== 1.6 QA features by Owner - RO ==
== All 1.6 Bugs that need to be verified ==
== 1.6 Bugs/features in needinfo ==
== 1.6 ALL Features ==
=== High ===
=== Medium+ ===
=== No of High and M+ ===
1.6 qa run history

Here you can find the current testing status for the latest weekly 1.6 Master branch
* 1.6 QA Status - QA Live status report
* 1.6 Distribution Tested
=== 1.6 Runs ===
==== 1.6 M1 ====
WW47 - 2013-11-19 - Weekly 1.6 M1
WW48 - 2013-11-27 - Weekly 1.6 M1
WW49 - 2013-12-03 - Full Pass Release 1.6 M1.rc1
==== 1.6 M2 ====
WW03 - 2014-01-14 - Full Pass Release 1.6 M2.rc1
WW04 - 2014-01-23 - Full Pass Release 1.6 M2.rc2
==== 1.6 M3 ====
WW07 - 2014-02-13 - Full Pass Release 1.6 M3.rc1
WW08 - 2014-02-18 - Full Pass Release 1.6 M3.rc2
=== 1.6 M4 ===
WW11 - 2014-03-12 - Full Pass Release 1.6 M4.rc1
=== 1.6 M5 ===
WW13 - 2014-03-26 - Full Pass Release 1.6 M5.rc1
WW14 - 2014-04-02 - Full Pass Release 1.6 M5.rc2
WW15 - 2014-04-11 - Full Pass Release 1.6 M5.rc4
=== 1.6.1 ===
WW24 - 2014-06-12 - Full Pass Release 1.6.1
WW26 - 2014-06-23 - Full Pass Release 1.6.1.rc3
=== 1.6.2 ===
WW44 - 2014-10-26 - Full Pass Release 1.6.2
WW46 - 2014-11-10 - Full Pass Release 1.6.2 rc2
=== 1.6.3 ===
WW12 - 2015-03-12 - Full Pass 1.6.3
WW20 - 2015-05-14 - Full Pass 1.6.3.rc4