> It’s reasonable to assume that when it goes to the Incubator people, they are > going to have another list of items to address that are again nothing to do > with the operation of the code.
Quite likely - I’m of the same opinion. So reducing the surface makes sense to me. Getting through all the way with a successful first step to release at least one of the repos is a sensible strategy given this is a first Apache release for the project. I looked through https://github.com/apache/incubator-openwhisk-client-go and it is the entirely self contained - all go code, no deps on other openwhisk repos. The readme doesn’t have a built step though (Or test although there are a handful of go tests in the repo). I also don’t see why we have to use different release numbers. Each of the components was broken out to make them independently managed so why couldn’t they all eventually be released as 0.9 as part of the overall first distributions? -r
