Prepare for 0.2.2

Author: oschwald

MaxMind.Db/Properties/AssemblyInfo.cs

@@ -2,7 +2,7 @@
 using System.Runtime.CompilerServices;
 using System.Runtime.InteropServices;
 
-// General Information about an assembly is controlled through the following 
+// General Information about an assembly is controlled through the following
 // set of attributes. Change these attribute values to modify the information
 // associated with an assembly.
 [assembly: AssemblyTitle("MaxMind.Db")]
@@ -14,8 +14,8 @@
 [assembly: AssemblyTrademark("")]
 [assembly: AssemblyCulture("")]
 
-// Setting ComVisible to false makes the types in this assembly not visible 
-// to COM components.  If you need to access a type in this assembly from 
+// Setting ComVisible to false makes the types in this assembly not visible
+// to COM components.  If you need to access a type in this assembly from
 // COM, set the ComVisible attribute to true on that type.
 [assembly: ComVisible(false)]
 
@@ -25,13 +25,13 @@
 // Version information for an assembly consists of the following four values:
 //
 //      Major Version
-//      Minor Version 
+//      Minor Version
 //      Build Number
 //      Revision
 //
-// You can specify all the values or you can default the Build and Revision Numbers 
+// You can specify all the values or you can default the Build and Revision Numbers
 // by using the '*' as shown below:
 // [assembly: AssemblyVersion("1.0.*")]
-[assembly: AssemblyVersion("0.2.1")]
-[assembly: AssemblyFileVersion("0.2.1")]
+[assembly: AssemblyVersion("0.2.2")]
+[assembly: AssemblyFileVersion("0.2.2")]
 [assembly: InternalsVisibleTo("MaxMind.Db.Test")]

releasenotes.md

@@ -1,5 +1,12 @@
 # Release Nodes #
 
+## 0.2.2 (2013-12-24) ##
+
+* Fixed a bug that occurred when using the memory-mode in a multi-threaded
+  application. When using a single `Reader` from multiple threads in memory-
+  mode, the internal state of the object could become corrupt if you replaced
+  the MaxMind database file on disk with another database file.
+
 ## 0.2.1 (2013-11-15) ##
 
 * Fixed bug that caused an exception to be thrown when two threads created a