GCC 5 is now the default in the wily release pocket, together with some libraries, which were either forced (icu, boost1.58), or migrated on their own.  The majority of the packages in -proposed are still blocked by missing rebuilds or packages failing to build.

The packages which already are migrated to the release pocket should be installable and not break any installation, however using the release pocket for development which touches any of the not yet migrated packages won't work.  For this case you have to enable the "proposed" pocket as well.

Updating your default environment to wily-proposed should at least work for the Ubuntu desktop, and this should be the environment for early adopters and adventurous users, but beware that it may brake with further changes.  Updates of Kubuntu, Xubuntu and UbuntuStudio desktops are not yet tested.  Feedback is welcome.

To get this large transition finished, your help is welcome and needed.

What you should *not* do:

 - Starting a major transition / update of some package or set of packages

 - Merging or force syncing a package from Debian which had a library
   transition in Ubuntu but not in Debian. We'll see to these packages
   after the majority of the packages moved to wily.

What you should do:

 - work on a transition mentioned at [1]. Pleases coordinate with
   release managers on IRC (#ubuntu-release).

 - Fixing build failures and dep-wait's mentioned at [2]. Check
   that page maybe not as often as your email, but do it on a
   regular basis. Unfortunately we had to start the GCC 5 changes
   with a rather long list of issues.

Remember that this transition doesn't end at the main/universe border or at the set of packages included in our iso images, but involves the whole archive (like any other transition).

Thanks, Matthias

[1] http://people.canonical.com/~ubuntu-archive/transitions/
[2] http://qa.ubuntuwire.com/ftbfs/