Caleb Shafer

> @ColinKerr we discussed making backend an optional dependency of ecschema-metadata, but i don't think that's right. @kabentley I think it should be a new package altogether that has the...

@kabentley can this PR be closed now that #4082 is merged?

@umerfaruque can you please provide the version of iTwin.js and the iTwin Viewer you're using? In addition, could you please provide the x-correlation-id, from the network tab in dev tools,...

@bear1004 yes, this repository has it's `master` branch currently working on the 3.3 release but if you'd like to test out from a 3.2.0 set of the source you can...

A while ago I implemented a naive [finalize release GH action](https://github.com/iTwin/itwinjs-core/actions/workflows/finalize-release.yaml) that would handle this sort of cherry-picking based on which release branch it was created on. There are currently...

This can be broken down into two main areas: - [x] Turn on Codeowner PR validation - [ ] Add build validation: - [ ] Main iTwin.js pipeline - [...

just turned on CodeOwner reviews required.

> Don't we have the option now to eliminate the imodel02 branch and most of the manual addon publishing process entirely? @pmconne not quite sure what you mean. Would you...

@DanRod1999 for now just do an apt install for the package you need as a script task in the build. We can update the actual image later. I can show...

closing this issue due to inactivity. feel free to re-open when providing more details.