Dave Enyeart
Dave Enyeart
I agree the k8s builder is very compelling, the key question here is whether it should remain a lab or become an official subproject. One thing that distinguishes a lab...
Thank you @dviejokfs ! @tock-ibm Any chance you could take a look? Core Fabric maintainers also maintain this fabric-config repository so would be good to get a maintainer familiar with...
I commented in the main [fabric APIv2 issue](https://github.com/hyperledger/fabric/issues/3650). > I would be in favor of updating all fabric repositories to APIv2 before Fabric v3 gets released (including Go chaincode repositories),...
@bestbeforetoday LGTM, any reason to keep it in Draft state?
@bestbeforetoday Apologies... today I noticed the apiv1 go dependencies were behind the apiv2 go dependencies so I opened pull request https://github.com/hyperledger/fabric-protos/pull/236. I had forgotten about this pull request until I...
@bestbeforetoday Agree we need to move to Node 20, but I think we need to figure out our release strategy first. I've traditionally told users that a major Node update...
> A data point to consider is that fabric-chaincode-node already switched from Node 16 to Node 18 between versions 2.5.2 and 2.5.3. Right, but we intentionally moved up to Node...
Good that it was built and tested against Node 18. But now that it is proven to work, do we need to continue to do that going forward? Or can...
@SamYuan1990 Thanks for moving this forward.
@dependabot rebase