Add blog post about v03x/v04x migration #27
Conversation
|
I'm not even sure a blog post is the perfect medium, but we can certainly use it to discuss and ship |
| ## The public gateways at ipfs.io | ||
|
|
||
| For the time being, https://ipfs.io uses both v03x and v04x to service requests. | ||
| Which ever responds successfully (2xx or 3xx status code) first, |
|
Overall, LGTM. However: what does this mean for me? Do I need to update my IPFS daemon? Do I need to update my server that uses IPFS? Something to clarify that would be good, I think. |
ghost
mentioned this pull request
|
Another thing that comes to mind is the question of whether v03x receives further patches/updates. It doesn't right now and it's not planned, but we should probably say so. cc @jbenet @whyrusleeping |
|
Addressed the feedback and open questions, and generally improved the thing. It's pretty good now I think. |
| --- | ||
|
|
||
| Good news everyone! We are about to release go-ipfs 0.4.0, | ||
| which contains lots of great changes and enhancements. |
There was a problem hiding this comment.
i think we want (to link to) a separate post about "the great changes and enhancements". can anyone pick this up? maybe @RichardLitt with help of @whyrusleeping and @diasdavid?
|
Okay addressed feedback |
ghost
mentioned this pull request
|
LGTM. |
Add blog post about v03x/v04x migration
|
thanks @lgierth! |
I think this has all the essential info. @RichardLitt @jbenet thoughts?