Che: Set up release for Dashboard Next

Created on 17 Aug 2020 · 6Comments · Source: eclipse/che

Is your task related to a problem? Please describe.

Currently, Dashboard Next is packaged into Che from next dockerimage image that we have at Che release time.

It was chosen as an easier way to go: the release of dashboard next is not really mandatory since we don't have fully complete basic workflows (it's kind of alpha phase).

It has a drawback because if we want to check which dashboard next snapshot is included into Che release - we need to figure out which image is included, find the corresponding commit in the Dashboard Next repo and then analyze history somehow.
It would be much easier if we start releasing Dashboard Next, technically it's pretty easy to implement but we need to agree on some aspects:

Does anybody see any issues in starting releasing Dashboard Next now?
Ideally, we should release alpha version, but from a release perspective, it's easier to follow Che versioning. Does anybody see any issues to release such alpha component as dashboard next as usual Che version, like 7.19.0, 7.20.0, ... ?

aredashboard kintask severitP2

Source

sleshchenko

❤1

Most helpful comment

Update: to avoid confusion with next word in two meanings (one is dashboard next, another is next changes from main branch), we agreed to the following tags: 7.X.X + next - existing dashboard, 7.X.X-react + next-react (Dashboard next which is react based).https://github.com/eclipse/che/issues/17647#issuecomment-704140948 is updated

sleshchenko on 3 Nov 2020

👍2

All 6 comments

@l0rd @nickboldt @mkuznyetsov WDYT?

sleshchenko on 17 Aug 2020

about about tags like 7.17.0-next

sunix on 18 Aug 2020

@sunix What the motivation to use next? next seems to indicate that it's rolling tag, but not release...
So, I would better go with the same versioning as Che has, che-dashboard-next:7.17.0
or if different versions not going to make our life more difficult - go with alpha, like che-dashboard-next:7.17.0-alpha or even che-dashboard-next:7.17.0-dev

sleshchenko on 18 Aug 2020

the problem with renaming the image name is that it will be hard to maintain: it is a new version of the dashboard and not anything else, not a new project. It will replace the current dashboard in the near futur. To me it sounds very confusing. If at some point we switch che-dashboard-next to che-dashboard what should we do for the "old" che-dashboard-next images ? somehow deprecate them ... => confusing and more work for us

If you could keep the image name, it would be simpler and more consistent for the futur.

There is nothing in 7.xx.x-next that indicates it is a rolling tag to me. But it could be 7.17.0-dev or 7.17.0-new or 7.17.0-dnext or 7.17.0-next-alpha or 7.17.0-dashboardnext

In the maven world, we have something called 'Qualifier' for these kind of things

sunix on 18 Aug 2020

👍1

@sunix Thanks for sharing your thoughts!
We're going to have the following:

Dashboard container is deployed as a separate deployment.
Dashboard image as previously lives in quay.io/eclipse/che-dashboard and is apache based server that serves dashboard resources.
Dashboard next lives in quay.io/eclipse/che-dashboard as well but is tagged as 7.X.X-react or next-react. It's based on the corresponding version of dashboard container + dashboard next resources.
Che Dashboard deployment is going to have next image by default. But users are able to configure non-next dashboard if they want.
One-day dashboard images are no longer built and dashboard-next becomes the usual dashboard with tags 7.x.x