This week still feels too soon for a rewards testnet.
Progress has been excellent over the past week with many pieces coming together, but there are still a few issues being observed and resolutions being worked on right now.
Will be the usual update later today with all the latest
I was recently complaining in another thread that @dirvine should stop giving out statements like “soon”, “few weeks” etc. in hopes that it would lessen my pre-dev anxiety (and maybe some others). But now I have found out that my skills in reading Github tealeaves have improved to the point that I was again sitting on the edge of my chair just based on my own assumptions. So thanks to @StephenC for letting me out of the hook again!
But boy, is it going to be a long week until next thursday… Maybe team Maidsafe should stop the work for a while right now and have an emergency meeting with a topic “How to get @Toivo a life.”
Yes, and most of the action is in the places where you would expect based on last Dev-Update. So the work seems to be concentrated on a few spesific issues - and proceeding well. No big surprises I guess - at least not yet. We have to remember that almost there ≠ there.
Then there are a bunch of other minor PR’s that are just filing the cornerns and refining the process here and there.
Noooo no haha, I promise I’m not up to any tricks!
Like you guys have noticed via GH, there has been great progress & a couple of big issues resolved, but there’s still another niggle or two that we’re investigating (and potentially others round the corner after we resolve them).
Since me not posting last week caused a bit of a stir…
Early notification that we believe this week is still too early to release a testnet. Still a few bits ongoing, e.g. in sn_routing where the bug fix PR mentioned at the end of last week’s update is in the process of being broken down into multiple smaller PRs so they are easier to review.
Thanks for your patience, full progress update as usual on Thursday.