Ab sofort können registrierte Entwickler via dem Developer Portal iOS 7.1 laden. Das Update gibts für alle Geräte welche auch iOS 7 unterstützen. Es wird gemunkelt, dass iOS 7.1 noch in diesem Jahr erscheint. Ein genauer Termin ist noch nicht klar.
Via BGR erreicht uns der aktuelle Changelog.

Notes and Known Issues
The following issues relate to using iOS SDK 7.1 to develop code.

Bluetooth

Known Issue32-bit apps running on a 64-bit device cannot attach to BTServer.

CFNetwork

Fixed in iOS 7.1 betaPreviously, if the server-side closed an HTTP request with TCP FIN without sending any bytes of HTTP header or HTTP body, NSURLConnection would synthesize an empty HTTP/1.1 200 OK response. This is now fixed, and the request will result in an error instead of a successful load with a synthesized response.

NotesA new compatibility behavior has been added to address an issue where some web servers would send the wrong Content-Length value for “Content-Encoding: gzip” content. Previously, NSURLConnection and NSURLSession would send a “network connection was lost” / NSURLErrorNetworkConnectionLost (-1005) error in this situation.
The compatibility behavior applies only if the Content-Length value exactly matches the expanded gzip’d content. It won’t apply for “off by 1” or similar miscounting.

Core Text

Fixed in iOS 7.1 betaPreviously, text drawn with CTFrameDraw did not correctly place lines to account for the paragraphSpacing attribute of NSParagraphStyle. This has been addressed in iOS 7.1 beta.

Crash Logs

Known IssueCrash logs will not appear in Diagnostics & Usage Data in Settings. The logs will still be available when synced off the device.

GLKit

Fixed in iOS 7.1 betaIf loaded with GLKTextureLoader, pngcrush images that have alpha were not unpremultiplied.

High Precision Timers

Fixed in iOS 7.1 betaWhen sleeping or waiting for extremely precise time intervals, timers were delayed by up to 1 millisecond.

iTunes

Known IssueLoading an iTunes Match library (or your purchased music history) may take much longer than expected, especially on larger libraries. If your library does not sync right away, please wait 30 minutes and try to access it again.