ipfs version 0.3.11 has been tagged as a release canidate. This will be the final release before 0.4.0. Once 0.3.11 is shipped, 0.4.0 will merge into master. This means we need to make sure a few things happen:

• 0.3.11 feedback
  • anything people want fixed before the 0.4.0 merge should be brought up now, not everything can be addressed, but major issues should receive some priority.
• migrations testing
  • @chriscool is doing a great job setting up CI for the fs-repo-migrations, once we get that working I will feel more confident in the migrations efficacy.
• ipfs distributions page shipped
  • this one is being blocked by me currently, but before we drop 0.4.0, users need an easy way to get access to the new versions and the migrations binary (without requiring them to have go installed)
• discussion about migration path
  • the biggest issue here is figuring out what network ipfs.io resolves through. I don't want a lot of bikeshedding here, so i'm thinking that a good way forward will be to have v04.ipfs.io for now point to nodes on the dev0.4.0 network, and have both ipfs.io and v03.ipfs.io point to the current network. Once v0.4.0 is officially released, we will make ipfs.io point to the v04 network.