Current Viewer Tier State

[wlongabaugh]

@fedorov @pieper cc: @madelyngreyes Current state of the tiers:

Dev: V 4.9.13 Build 137
Test: V 4.9.7, Build 123 (March 31)
Production: V 4.9.5, Build 121 (March 30)

When wanting to push from dev to test, or test to prod, please submit an issue here, and please let me know via Slack or email. If you wish to annotate with e.g. the major feature(s) of the version from IDC's perspective, this might be a good way to track it.

[madelyngreyes]

@fedorov @pieper hello, the viewer on the IDC test tier, doesn't work for segmentation. I believe it needs to updated with the IDC viewer version that's on the dev tier.

[pieper]

Thanks for checking @madelyngreyes - Bill handles that side of things and he likes to get pinged on Slack when a new version needs to be deployed.

[fedorov]

@madelyngreyes can you provide the example where it does not work? This must be a regression, since I believe it works in production, and test (at least according to Bill note on top) is ahead of production. I am not sure upgrading will resolve the issue.

[madelyngreyes]

From the homepage, the selection of a CT option.

Screen.Recording.2021-05-13.at.7.04.04.PM.mov

[fedorov]

You need to drag SEG into the viewport.

[madelyngreyes]

Yes, was able to get it working. Thank you for the clarification.

[wlongabaugh]

OK, current status is that one or two pull requests will be merged with dev in the near future, then I will get a notice here that we are ready to pull to test.

[Punzo]

@wlongabaugh I just merged into master version 4.9.17 (#87). Could you please update dev and testing portals (if @fedorov agrees)? @pieper could you please also update sandbox?

[fedorov]

I agree

[wlongabaugh]

Testing portal is updated.

Current state of the tiers:

Dev: V 4.9.17 Build 141
Test: V 4.9.17, Build 143 (May 19)
Production: V 4.9.5, Build 121 (March 30)

[fedorov]

@wlongabaugh test tier viewer is working fine based on @madelyngreyes testing. Can we update the production tier?

[wlongabaugh]

@fedorov @pieper @madelyngreyes Released to production, backed by proxy with new scaling configuration:
Dev: V 4.9.17 Build 141
Test: V 4.9.17, Build 143 (May 19)
Production: V 4.9.17, Build 145 (May 24)

[fedorov]

It feels so refreshing not to have to do hard reload and clear cache!

[fedorov]

@wlongabaugh the fork has been updated, and it it would be great to update test tier whenever you get a chance.

[Punzo]

Igor updated the fork to version 4.9,19, see #91

[wlongabaugh]

@fedorov @pieper @madelyngreyes Viewer updated in test:

Dev: V 4.9.20 Build 147 (June 3)
Test: V 4.9.20, Build 149 (June 3)
Production: V 4.9.17, Build 145 (May 24)

[fedorov]

Thanks! Just in time for @madelyngreyes testing in preparation to v2 release.

[wlongabaugh]

@fedorov @pieper @madelyngreyes Viewer updated in prod: (But investigating that it still points at v1?)

Dev: V 4.9.20 Build 147 (June 3)
Test: V 4.9.20, Build 149 (June 3)
Production: V 4.9.20, Build 153 (June 15)

[wlongabaugh]

The prod version was old and thus I think it still had a sticky cache. It is now requesting V2 content.

[wlongabaugh]

@fedorov @pieper Has 4.10.1 been approved to push out to test and (next week) prod?
Dev: V 4.10.1 Build 167 (Sept 13)
Test: V 4.9.20 Build 149
Production: V 4.9.20, Build 161

[pieper]

I have not tested it, but the changes were small so I'd suggest putting it in the testing tier and letting people know they should kick the tires.

[wlongabaugh]

Fine with me. We can always hold prod at 4.9.20 if anything crops up.

Bill

[wlongabaugh]

And now we are sitting here:

Dev: V 4.10.1 Build 167 (Sept 13)
Test: V 4.10.1 Build 169 (Sept 20)
Production: V 4.9.20, Build 161

[wlongabaugh]

And now we are sitting here:

Dev: V 4.11.2 Build 176 (Oct 1)
Test: V 4.10.1 Build 169 (Sept 20)
Production: V 4.10.1, Build 174 (Sept 27)