Definitely check out this podcast. ICEFaces is a very exciting technology because it is both innovative and efficient. The team is very focused on making JSF more compelling than trying to do Ajax by hand with jQuery or Dojo. Much of what Ted talks about just got included in the forthcoming version of Chapter 12 from Seam in Action.
Do you prefer Richfaces or ICEFaces currently?
Do you think your preference might change with the release of JSF 2.0
I would say it depends. If I wake up feeling like I need tons of rich-client elements on my page, then I have to go with RichFaces because it is just ridiculous how many components it has. On the other hand, if I want Ajax fast and free, then ICEFaces gives me that, and that is what I would prefer. Also, Ajax Push is only done right with ICEFaces (the RichFaces solution is sort of an after thought). Another thing is RichFaces responses are typically larger than ICEFaces reponses.
You are likely going to need both, at least for the time being. I doubt JSF 2.0 will really impact users all that much (aside from the standardization of Facelets). It will really just make component libraries perform better or in a more consistent way.