You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 27, 2023. It is now read-only.
This issue is to discuss which branches should tests against which Kibana version.
Currently, CI spins up a 8.0.0-SNAPSHOT cluster and tries to load the packages into. But in reality, all the packages we release are for ^7.9.0. This means we test against a version which is not actually the one in the end used. Historically this made sense as all the development / major chanegs were in 8.0.0-SNAPSHOT first but now that we are slowing down the pace and features we need are directly in 7.9 and later, I suggest we change against which version we test. This also solves the problem that some packages might not show up in Kibana because of the ^7.9.0 limitation.
Proposal
In the ideal case, I think we should test with the minimal version a package supports. Currently for most packages this is 7.9.0-SNAPSHOT. The problem with 7.9.0-SNAPSHOT is that AFAIK it will disappear soonish after 7.9.0 is shipped. This means, each time a new minor is out, we need to update to a new snapshot. This means 7.10.0-SNAPSHOT. I think this is acceptable. Long term, we should test against multiple versions (released and unreleased once).
The other question was if all branches should use the same version or snapshot should depend on a more recent one. But to have consistency during development, I think it is most predicable if all point to the same version.
This issue is to discuss which branches should tests against which Kibana version.
Currently, CI spins up a
8.0.0-SNAPSHOTcluster and tries to load the packages into. But in reality, all the packages we release are for^7.9.0. This means we test against a version which is not actually the one in the end used. Historically this made sense as all the development / major chanegs were in 8.0.0-SNAPSHOT first but now that we are slowing down the pace and features we need are directly in 7.9 and later, I suggest we change against which version we test. This also solves the problem that some packages might not show up in Kibana because of the^7.9.0limitation.Proposal
In the ideal case, I think we should test with the minimal version a package supports. Currently for most packages this is 7.9.0-SNAPSHOT. The problem with 7.9.0-SNAPSHOT is that AFAIK it will disappear soonish after 7.9.0 is shipped. This means, each time a new minor is out, we need to update to a new snapshot. This means
7.10.0-SNAPSHOT. I think this is acceptable. Long term, we should test against multiple versions (released and unreleased once).The other question was if all branches should use the same version or snapshot should depend on a more recent one. But to have consistency during development, I think it is most predicable if all point to the same version.