[racket-dev] Release Announcement for v6.1.1, Second Draft

The release announcement sketch that I have so far is below.  Please
mail me new items and/or edits.
----------------------------------------------------------------------

Racket version 6.1.1 is now available from

     http://racket-lang.org/

* Mac OS X Yosemite: fixed compatibility problems, mainly by patching
   the Pango text-drawing library that is bundled with Racket.

* Windows, 32-bit version: fixed window-update crashes by patching
   the Cairo drawing library that is bundled with Racket.

* Windows: made the GUI library DPI-aware.

* Added a "binary library" installation mode to install packages
   without source or documentation. Use the `--binary-lib` option
   with `raco pkg install`.

* Repaired the compiler's use-before-defined analysis for certain
   forms of nested `letrec`, some `let` forms, and some uses of
   `set!` or `with-continuation-mark`.

* Added bytecode optimizations (thanks to Gustavo Massaccesi).

* Added a `replace-evt` event constructor (as suggested by Jan Dvořák).

* Added the drracket/check-syntax library to facilitate check
   syntax-like behavior in other IDEs.

* Redex: explained the benchmark programs added a conditional-form
   to metafunctions.

* 2htdp/image's notion of equality no longer considers an image's
   baseline.

* Contracts: contract-stronger? is now more consistently useful
   and contract error messages now admit the contract itself might
   be wrong.

* Exception handling changed to be safe. This may break existing
   programs that rely on unsafe behavior.

* Casts and predicates are supported in typed regions.

* The `openssl' library supports Server Name Indication for server
   contexts (thanks to Jay Kominek).

* The `syntax/parse' library allows the definition of new pattern
   forms via pattern expanders, similar to match expanders (thanks
   to Alex Knauth).

* For OpenGL on Linux, removed dependence on libgtkgl and added
   support for core profiles (see `set-legacy?`).

* The unit test framework for the *SL teaching languages supports
   check-satisfied, a construct for checking whether a result
   satisfies a named predicate, e.g.:
     (check-satisfied (sort l) sorted?)

----------------------------------------------------------------------