You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey everyone, I've told a few people about this, but now more broadly:
I'll be traveling with family from 12/18 - 1/5
(going to New Zealand!) I will have sporadic internet access, but will only be attending to very pressing things-- hotfixes, emerging issues, and so on. If I don't get to your PRs, comments, messages, or email, please be patient. Occasionally, I may address longer discussions and some CR, but it would be very high latency.
If you need to reach me urgently, email me and tag the subject with URGENT:, like so:
Subject: URGENT: everything exploded!
Thanks! See you soon :)
On go-ipfs
go-ipfs is the most important repo I maintain. Things should wait for my CR before merge, except for the following (CRed by several people pls):
bugfixes that bring master back to green
more tests
things for merging 0.4.0
On merging 0.4.0
The big thing coming up is merging dev0.4.0 into master. If happens before I return, I can make time to CR this, as it is very important. (most of it is CRed already, so shouldn't be a big thing).
I think the https://ipfs.io gateway should resolve content on both networks
Maybe we should enable the new handshake as another swarm addr for now, and overtime (by 0.4.x or 0.5.x) remove it with a migration. (i.e. people with 0.4.x could run both protocols for now)
The text was updated successfully, but these errors were encountered:
Hey everyone, I've told a few people about this, but now more broadly:
I'll be traveling with family from 12/18 - 1/5
(going to New Zealand!) I will have sporadic internet access, but will only be attending to very pressing things-- hotfixes, emerging issues, and so on. If I don't get to your PRs, comments, messages, or email, please be patient. Occasionally, I may address longer discussions and some CR, but it would be very high latency.
If you need to reach me urgently, email me and tag the subject with
URGENT:
, like so:Thanks! See you soon :)
On go-ipfs
go-ipfs
is the most important repo I maintain. Things should wait for my CR before merge, except for the following (CRed by several people pls):On merging 0.4.0
The big thing coming up is merging dev0.4.0 into master. If happens before I return, I can make time to CR this, as it is very important. (most of it is CRed already, so shouldn't be a big thing).
0.4.x
or0.5.x
) remove it with a migration. (i.e. people with0.4.x
could run both protocols for now)The text was updated successfully, but these errors were encountered: