Sample partial README file for EE 1.13

RELEASE_NOTES_EE-sample.txt

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
] NOTE: For up-to-date information that came to light after these Release Notes  [
] were added to this build, go to:                                               [
]                                                                                [
] http://www.magentocommerce.com/knowledge-base/entry/ee-113-later-release-notes [
]                                                                                [
] In the future, you should always get Release Notes from magentocommerce.com.   [
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

==== 1.13.0.0 ====

==== Highlights ====
Average load time of less than two seconds on all pages (1,000 user test)
Major overhaul of tax calculation formulas, correction of rounding errors, and additional assistance with configuration
Most indexing processes now run only to update products, categories, URL redirects, and so on that have changed—eliminating the need for manual full reindexing
Additional option of using Redis NoSQL for cache and session storage in multi-host deployments (recommended for new deployments)
Full page caching now invalidates only pages that are affected by product, page, or category changes
Elimination of many types of database deadlocks
Optimized cache adapters for single-server systems

==== Security Enhancements ====
The Magento Admin Panel and web stores no longer allow web browsers to store user names or passwords.
The Magento web store has additional Cross Site Request Forgery (CSRF) protections, meaning an imposter can no longer impersonate a newly registered customer and perform actions on the customer's behalf.
In earlier versions, Magento was vulnerable to a session fixation attack during the registration process. After logging in to their account, a registered user's session ID did not change. Therefore, if an attacker had knowledge of an unauthorized session ID and if that user successfully registers, the attacker was able to take over the newly registered account.
Now, the session ID changes after successful registration, making unauthorized use of an account impossible.
The cryptographic methods used to store passwords were improved to enhance security.

==== Performance Improvements ====
Completion time for fully reindexing URL redirects (formerly referred to as URL rewrites) has been reduced from four hours to four minutes for a database with one million products
URL redirect reindexing time increases in direct proportion to the number of products in your database
Checkout performance improvements achieved by:
* Eliminating unnecessary calls to gift wrapping when loading the Shipping Method checkout step
* Eliminating unnecessary RSS cache cleanups when RSS functionality is disabled
* Eliminating unnecessary calls to the translation module when sending new order e-mails if the current locale is the same as the locale set in Magento
* Improving the overall checkout process performance by loading the information for the current checkout step only
* Improving the overall checkout process performance by loading the progress information for the current checkout step only
You can load a large number of tax codes (35,000 or so) without impacting performance. 
The locale used to send a new order confirmation e-mail now first checks to see if the customer's locale is the same as the store's locale before attempting to localize the e-mail. As a result, it now requires 5% less time to process the order. 
Magento uses Materialized Views for database access, which dramatically reduces processing time and overhead
Magento uses MySQL database triggers to improve access to the database during reindexing.