Release?

[metacosm]

Type of question

Open question

Question

When will this project be released? What will be the release frequency?

[laxmikantbpandhare]

Type of question

Open question

Question

When will this project be released? What will be the release frequency?

This project is already released as an alpha release of Java plugin. We release it with operator-sdk releases. We do it every 3 weeks.

[metacosm]

There is no release of this project. The version used in operator sdk is referenced via a commit id in go.mod which makes it complex to figure out which version of the plug-in is used in a given operator sdk release.

[laxmikantbpandhare]

As part of this PR, we integrated java-plugin with Operator SDK and released in v1.8.0. We are able to scaffold out java-operator-plugin files using Operator SDK. Yes, it is difficult to see which version of plug-in is released. Maybe @jmrodri can help on this more.

[metacosm]

The whole point of this question is about having released versions that can be referenced for this plugin. I very well know that the plug-in is bundled in the operator sdk. That's not the question.

[laxmikantbpandhare]

okay. I got your point. Need to have released versions for this plugin.

[jmrodri]

So what I was thinking is the following:

• use semver for the versions, say starting with 0.1.0
• for now I say we could adapt this script to release the project similar to operator-lib. keep it simple: https://github.com/operator-framework/operator-lib/blob/main/release.sh

Phase 2 plugins will make it such that we could actually release a binary for this project but until then the releaess will just be github releases with zip and tarball releases. Then updates to the operator-sdk repo.

[metacosm]

@jmrodri whatever works as long as we have something more easily referenceable 😉
+1 on semver