-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 2.10 #5211
Comments
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Agreed in dev call 2021-05-27 to go ahead with branch. |
@sarbull @lpalashevski @bogdan-sava If you wish to create a new version of the UI for us to use in our helm charts etc please post here. Without any further change, we will point to a docker image 2.8.0 (see https://hub.docker.com/repository/registry-1.docker.io/odpi/egeria-ui/tags?page=1&ordering=last_updated) |
#5211 update master to 2.11-SNAPSHOT
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Testing currently blocked due to :
See #4046 - previously identified. This is a limit for all users. the counter does reset within 6 hours, but it's an indication other users of the egeria repo could get into difficulty and we need to urgently consider an alternate repo for egeria images such as quay.io, possibly publishing to both locations |
CTS inmem successful:
|
Notebook
Polymer UI
React UI
|
Lets keep 2.8.0 in the charts for this release since we have not published new version for egeria-ui. Recently there was major refactoring so we still need to polish out few details (#5238 might be related to this or some additional default configuration we are missing for the backed api) |
Currently the helm chart does indeed point to the 2.8.0 release, but perhaps so is ongoing development, so the image continues to evolve. We really need to target a fixed code level for integration with demos etc. We could go back to 2.7.0 ? Or we retrospectively create a branch from an appropriate point to capture a 2.8.0 release? For the react ui we have master/main containing something like 2.10.0-rc.0. Then when we branch we update that to '2.10.0' and change main/master to 2.11.0-rc.0 . The docker image ci/ci process takes the version number to use for the label of the docker image. this way when egeria 2.11 ships, it points to egeria-react-ui image 2.11.0 which will not change, so should be stable. For the components we use in the images we know multiple people are using I think we need to go through that stabilization as testing on the UI side in concert with the egeria base. It can lag a release or more, that's fine, but some testing or ideally automation is needed for the polymer UI as currently I am unable to test it as thoroughly as I would like (sample data, scripting, notebook etc) It may be easier to manage if we deploy the UI independently - it could be a seperate helm chart for example , that would make it easier for the UI team to test in compose and k8s without being overly concerned with deployment of the base components? This would lead us to remove it from the lab chart, where in any case it isn't currently really documented or have any supporting materials |
Graph CTS has completed successfully with:
|
…nloads Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Currently blocked on #5241 Alternatives Leave UI as broken, add note to readme |
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Note when testing react ui - see odpi/egeria-react-ui#41 (/coco fails, /coco/login works ok) |
#5241 is now fixed, polymer UI is now ok in 2.10 |
Testing now complete |
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
Signed-off-by: Nigel Jones <nigel.l.jones+git@gmail.com>
2.10 was released on github & maven central on 2 June. |
Create 2.10 release
The branch for 2.10 release is 27th May 2021 (agreed community call, 20 May 2021)
The text was updated successfully, but these errors were encountered: