Allow other templates to supply og tags
Only truncate description if one is provided
Sharing: Check if label value is set before to display it

For more details, check the original trac ticket:
http://plugins.trac.wordpress.org/ticket/1974
Widget visibility: Add support for old-style single widgets
Props @westonruter

For more details, view the original ticket:
http://plugins.trac.wordpress.org/ticket/1979
Modifies the Image Widget to allow basic HTML in the caption.

Allowed HTML: a[href, title], b, em, i, p, strong
Widget visibility: widget should not appear on paginated home page

Unless a theme supports Infinite Scroll, hide widgets  on paginated home page

You can read more about it in the original ticket here:
http://plugins.trac.wordpress.org/ticket/1989
Enable Freshly Pressed for Jetpack Blogs

Enhanced Distribution: Add a server-side catch that will return JSON
data if ?get_freshly_pressed_data=true
-- will return the WPCOM Blog ID and Post ID (both of which are
probably accessible on the page already, but
this simplifies things and confirms that the Enhanced Distribution
module is enabled (as we wouldn't want to
Freshly Pressed a post otherwise).
Fixes whitespace
CSS: avoid notices to be displayed over WP submenus
Post Images: grab images when HTML uses single quotes
Media Extractor: avoid notices when preg_match fails

More details here:
http://wordpress.org/support/topic/non-robust-code-in-jetpack_media_meta_extractorget_images_from_html
Media Extractor: pass all variables to isset()

See #46
Jetpack: SSO: Adding remote disconnect from wpcom XMLRPC endpoing
Jetpack: Multisite: Adding Multisite branch to Github
Jetpack: Multisite: Removed debugging preventing get_default_modules from firing
Jetpack: Multisite: Updating tests
Merge branch 'multisite' of github.com:Automattic/jetpack into multisite
Jetpack: Multisite: Updating tests to use instance instead of instantiation
Jetpack: Multisite: Updating tests
Multisite: Activate modules when new sites are created.

If Jetpack is on a single-site installation, or is not network-activated in a multisite installation, then modules get activated automatically when the plugin is activated.

In a Multisite installation where Jetpack is network-activated, though, that doesn't happen unless we trigger it inside a wpmu_new_blog callback.