Eneko Fernández
Eneko Fernández
> @lizwarner-weave is there a dedicated URL to install weave scope as well ? The installation instructions still refers to cloud.weave.works (https://www.weave.works/docs/scope/latest/installing/#k8s) @lucj looking into this
@lucj see the update on [scope docs](https://www.weave.works/docs/scope/latest/installing/#k8s) let me know any feedback at the back of it
@jpellizzari @luizbafilho would it be possible to add to the epic the links of the pieces of evidence that you have around this epic?
> Could you be a bit more specific? it's not clear to me what evidence you want. Sure sorry, I mean the evidence for the performance tests that you have...
> I don't have anything, it was the code itself, and by checking how k8s clients work. Ahh no probs, just was in case you had it to reuse it...
- licensing under entitlements - clear integration points between OSS and EE and how this situation enhances
@jpellizzari adding notes out of scoping conversation for q2 planning
@LappleApple just mentioned in our product engineering roundtable that we could leverage her opensource strategy experience ... i thought it would be useful here!
reduce release container image build time and github release should happen after artefacts are ready
enhancement -> build time bug -> release order
reduce release container image build time and github release should happen after artefacts are ready
>GitHub release happens before artifacts are available: it matters cause the github release flags the community that a new release exists. Given that weave gitops would be mostly usedin containerized...