@ryotsuke - Hi! The changes to i2c is in git, but not yet pushed to the compile server. The firmware team plans to release 0.4.0 as soon as all tests are done (currently targeting today or tomorrow). Then the release process to the compile server can happen shortly after that, maybe available Monday or Tuesday.
1 Like
Update — release will probably be early next week. The firmware team has made some pretty epic changes under the covers lately. We need some more testing time to ensure everything still works as expected, and then the firmware and cloud teams will have to coordinate on the deployment since the build scripts have had some significant updates.
2 Likes
That’s really some set back but I do understand the importance of quality. Keep up the good work and hope to see a reliable I2C implementation soon.
1 Like
And just to keep everyone abreast of the rapidly changing status, we’re going to defer the big release and instead do a smaller release with just the I2C and similar changes. 
4 Likes
@zachary, how would this affect the release schedule and what would be the latest ETA?
Hoping to cherry pick the appropriate commits tonight (possibly tomorrow) and tag a release. Once I get that done, we’ll deploy as soon as the cloud team has some spare bandwidth, hopefully tomorrow.
1 Like
I’m starting on the merging / cherry picking now. Proposed pull requests to include 305, 315, 320, 322, 327. I’m basically live narrating my progress in the #spark IRC channel on Freenode for those that want to follow along/discuss.