I think a release vote is appropriate, though whether or not it needs 3 +1s or can be done by lazy consensus is a detail to explore. Since this is a metapackage type thing, I can see it being done either way as it's similar to a parent pom in the Java world where you're just referencing several already released components.
On Thu, 19 Nov 2020 at 15:26, David P Grove <gro...@us.ibm.com> wrote: > > > > Hi, > > With the recent completion of the OpenWhisk 1.0.0 release, we are almost > ready to make our first unified release. As discussed quite a while ago, a > unified release simply bundles a compatible set of already-released > components into a time-based version number. The goal is to make it easier > for users to be able to download a complete set of all of our components > that are known to work together. > > To finally finish this process, we need to do two things: > > 1. Make a release of openwhisk-deploy-kube 1.0.0. There is a 1.0.0 branch > that is very close to being in final state. I hope to finalize it this > week and kick off a formal release vote. > > 2. Create a subdir 20.11 in our distribution svn and replicate the current > set of most-recent releases into it. Bertrand, Matt, and other ASF > experts. What is the correct process for this? Do we do a release VOTE on > a 20.11 meta-package by listing the already released artifacts that we are > going to bundle together in a VOTE thread? > > thanks, > > --dave
