Provides a nightly image for che-theia image on branch 7.0.0

[benoitf]

Description

There is a 7.0.0 branch in che-theia for stabilizing che/theia used for 7.0.0 GA

but AFAIK there is no nightly image built from that branch so any new commit to 7.0.0 is not used on che master branch (7.0.0 branch)

So if the tag is only occurring at the end it might not work at all and people are not using the latest state.

Before che:master was using che-theia:next but it can't be the case anymore as process it to have something as stable as possible.

[tsmaeder]

Tagging this 7.0 because it's necessary for testing our work for 7.0

[evidolob]

che-theia 7.0.0 branch builded on each commit.
After this pull eclipse-che/che-theia#347
che-theia docker image has 7.0.0-rc-4.0-SNAPSHOT version.
Also 'latest' tag points to 7.0.0-rc-4.0-SNAPSHOT

[benoitf]

should it be 7.0.0-next to match the other kind of master version which is next ?

[evidolob]

It can be, but I want to alight che-theia image version with Che version

[benoitf]

but che version images are 'nightly' (there is no SNAPSHOT in all other che images)

[evidolob]

OK, so version should be 7.0.0-nightly ?

[benoitf]

if you name it nightly but it's built at each commit there is something wrong, this is why it ended it up with next

latest and next are the existing keywords used

[evidolob]

@benoitf It seems your comment not full, can you write what version you think would be better?

[benoitf]

@evidolob

7.0.0-nightly if it is built every night
7.0.0-next if it is built at each commit

Now, it means that plugin-registry is updated a lot so if you're able to give a word to 7.0.0 it may be better.

For example some products have channels like edge, stable, testing, unstable, etc

so you could say:
next is from master branch
testingor another keyword is from the master branch or from the current code freeze branch (if there is one at a time)
latest is the latest stable version

etc

so we have channels instead of versions

[evidolob]

OK, it would be 7.0.0-next I'm going to create PR

[vparfonov]

@evidolob

7.0.0-nightly if it is built every night
7.0.0-next if it is built at each commit

Now, it means that plugin-registry is updated a lot so if you're able to give a word to 7.0.0 it may be better.

For example some products have channels like edge, stable, testing, unstable, etc

so you could say:
next is from master branch
testingor another keyword is from the master branch or from the current code freeze branch (if there is one at a time)
latest is the latest stable version

etc

so we have channels instead of versions

So in this case 'latest' will be the same for each Che backend for 7.0.0-rc-4.0 and for 7.0.0 and probably won't work in some cases.

[benoitf]

@vparfonov for tagged versions we replace aliases by the real versions so latest inside 7.0.0 will still have 7.0.0 everywhere ( a tag is a fixed name)
but SNAPSHOT, nightlies, etc, all are for development purpose.

the backend for 7.0.0-rc-4.0 and for 7.0.0
if you use che latest at some point you'll get 7.0.0-RC4 and then 7.0.0 but you'll never have a mix.

if you use 'latest' then you've the latest stable version of che, latest stable version of theia, etc
and for testing you would have the testing version of che, etc
if you use nightly then you should have nightlies everywhere, etc.

[evidolob]

I think we can close this issue, che-theia:7.0.0-next is updated on each commit in che-theia 7.0.0 branch, so we don't need to have nightly image.