[che-dev] Che plugin brokers refactor is merged

[Angel Misevski <amisevsk@xxxxxxxxxx>]

Hi all,

Today I merged a large refactor to the Che plugin brokers (Issue: [1], 
PR [2]). One of the changes in this PR is that the earlier broker images 
(che-plugin-init-broker and che-plugin-unified-broker) are deprecated in 
favor of the new images:

- che-metadata-plugin-broker
- che-artifacts-plugin-broker

I'm preparing to release the new brokers soon, but this change brings up 
two questions I wanted to get feedback on:

1) To release the brokers, new image repositories will need to be 
created. As we are generally trying to move Eclipse Che images over to 
quay.io/eclipse instead of dockerhub, now seems like a good time to make 
the change. Are there any complaints with moving the brokers over to 
quay.io?

2) What is the 'next' plugin broker version we release? Thus far, we 
have been using exclusively minor releases for plugin brokers, and 
currently we're up to v0.24.0. This is a strange way to version the 
project, since many of our minor releases are backwards-incompatible and 
thus should have resulted in a major version bump. I think, 
retrospectively, a sensible way to version would at least be

- v1.0.0: First non-beta release, coinciding with Che 7 (actual release 
is v0.19)
- v2.0.0: Addition of remote binary injection from Theia (actual release 
is v0.22)

as a result, I'm inclined to release the brokers as version v3.0.0 now, 
and go forward with using semantic versioning as intended. Are there any 
issues with this?

Regardless, the release and merge to Che master is blocked for now, 
since we would need to either create new repositories on dockerhub or 
quay, so I'll check in on Monday and look to complete the process.

Cheers,

Angel


[1] - https://github.com/eclipse/che/issues/14494
[2] - https://github.com/eclipse/che-plugin-broker/pull/80