X-Git-Url: https://wimlib.net/git/?p=wimlib;a=blobdiff_plain;f=NEWS;h=8c54a2376c1614e6e3ae1136c9d43d262aca8571;hp=221126a444fe2c723719744512155fcce6f07899;hb=4efdef43a8bb9e821f39572e1c9086e3f069ac7c;hpb=ff3ce0b70ec73e75a30b693c04c34b90cc853796

diff --git a/NEWS b/NEWS
index 221126a4..8c54a237 100644
--- a/NEWS
+++ b/NEWS
@@ -1,5 +1,48 @@
 Only the most important changes more recent than version 0.6 are noted here.
 
+Version 1.6.3-BETA:
+	Added support for "WIMBoot".  On any platform, you can now capture a WIM
+	as WIMBoot-compatible.  In addition, on Windows, specifically Windows
+	8.1 Update 1 and later, you can now apply a WIM archive in a special
+	mode that causes extracted files to be externally backed by the WIM
+	archive.  See the documentation for the new '--wimboot' option to
+	wimcapture and wimapply, respectively, for more information.
+
+	The shared library version has been bumped up; however, there are only
+	a few incompatibilities:
+
+		- WIMLIB_COMPRESSION_TYPE_XPRESS is now 1 and
+		  WIMLIB_COMPRESSION_TYPE_LZX is now 2 (so it's the same as
+		  WIMGAPI).
+
+		- 'struct wimlib_capture_config' has been removed.  The library
+		  now takes the path to the configuration file directly.  This
+		  affects wimlib_add_image(), wimlib_add_image_multisource(),
+		  and wimlib_update_image().  However no code changes are
+		  necessary if a NULL configuration was being used.
+
+		- Removed deprecated functions: some (de)compression functions,
+		  wimlib_extract_files(), and wimlib_print_metadata().
+
+		Otherwise the API and ABI is the same.
+
+Version 1.6.2:
+	Case-insensitive comparisons of strings (e.g. filenames) containing
+	UTF-16 codepoints above 32767 are now done correctly.
+
+	Fixed build failure on Mac OS X.
+
+	wimunmount now provides the '--new-image' option to cause changes to a
+	read-write mounted image to be committed as a new image rather than as
+	an update of the mounted image.  (The corresponding new library flag is
+	WIMLIB_UNMOUNT_FLAG_NEW_IMAGE.)
+
+	The LZMS ("recovery") compression chunk size, or "dictionary size", may
+	now be up to 1 GiB (1,073,741,824 bytes).
+
+	The performance of LZX ("maximum") and LZMS ("recovery") compression
+	with large chunk sizes has been slightly improved.
+
 Version 1.6.1:
 	Stored files with size exactly 4 GiB (4,294,967,296 bytes) are now
 	decompressed correctly.
@@ -10,7 +53,7 @@ Version 1.6.1:
 
 	Fixed a minor compatibility issue with the LZMS compressor and
 	decompressor.  This is *not* the default compression type and was only
-	introduced in v1.6.0.  In the unlikely event that you created a
+	introduced in v1.6.0.  In the unlikely event that you created an
 	LZMS-compressed WIM with v1.6.0 and a checksum error is reported when
 	applying it with v1.6.1, decompress it with v1.6.0 then compress it with
 	v1.6.1.