Looking forward to the roadmap details but some general snippets of interest first:
New seamless retrieval discussed – see my previous post:
http://jamesjallen.me/2011/06/30/icc-transparent-retrieval/
Sharepoint Best Practices – new ICC deployment approach to SP front end server.
Big focus on SP – improved stubs, integration with metadata.
Delete in P8 – clear up stubs in SP now
Maintain original dates and icon for filesystems – previously the modified dates changed.
ICC 2.2 FP1 support for:
> P8 5.0 with Content Search Services
> Support for SQL server 2008 R2
> Option to disable icon changes in LN email stubbing
Roadmap:
ICC 2.2 FP2: support for p8 5.1 with CSS, IE9, Improved SP columns eg, calculated / multivalue columns, CM8 Text Indexer support for CSLD legacy itemtypes
2012 Q2 – release planned, Connectors to IBM Connections, Expand SP Support – seamless checkin, automatic stub deletion for emails & files, improved historical monitoring, improve performance for mailboxes
2013 2nd half – might be the next release
Questions:
Around Quickr and ST integration – ST there is a partner (but there is a undocument switch to write ST chats out to local filesystem as text 
Quickr – no plans as discussion suggested it would integrate into Connections! WOW 
Single search interface – plans to merge EDM into Outlook and Notes local search.
P8 5.1 Content Search Services: IBM want to own support for indexing as in past issues occur and they rely on Verity which they cannot influence the turn around. CSS built on text indexing engine Apache Lucene (Used in dozens of IBM products). Benefits – larger index sizez, monitoring, thru’ put, scaling all better.
A new email data storage model based on xml files (sounds bit like CM8 NSE indexing )
2.2.0.2 benefits:
> Reduce storage costs
> Reduced load on FileNet P8 CE servers
> Improved indexing throughputs (1.25 – 1.5 times performance / multi lingual)
> Improved monitoring.
