search

eclipsesource / theia-cloud-helm

Eclipse Public License 2.0
3 stars 6 forks source link

Update to 0.9.0 #47

Closed sgraband closed 5 months ago

sgraband commented 5 months ago

Update version and appVersion. Regenerate READMEs.

Contributed on behalf of STMicroelectronics

sgraband commented 5 months ago

Tested all configurations and they work fine with 0.9.1 :partying_face:

sgraband commented 5 months ago

I see, and we can certainly do this for this update, but what would you expect to happen, if we really would have a backport after we already started to create next versions for the upcoming version?

Would we then also contribute the version numbers back to main? Because then we would have a history with version numbers like this (bottom to top):

0.10.0-next 0.9.2 0.10.0-next 0.9.1 0.9.0 0.9.0-next

Would that be fine? I think the main problem that we have here, is that the terraform configurations are in the source repo. We could also only update the terraform values on the main branch if that happens?

jfaltermeier commented 5 months ago

It depends I guess. At least we need a task to think about if a backmerge/cherry-pick is needed.

Versions that point to a release should always point to the latest release in my opinion. (I guess this will mainly affect terraform) We should not override 0.10.0-next with a 0.9.x version on a backmerge though.

I think the rule of thumb is, if there is a conflict on a version, take the changes from main.

sgraband commented 5 months ago

Ok great! I created a Template task for this. I think we can discuss this, when it arises. Thanks for the feedback. I will open a PR on the main repo that updates the versions to 0.9.1