10:29 a.m.
Hi folks,
For [1], I think it cannot be done for the current milestone, so lets take it out. We need
to create a new private git repo, generate deployment keys, then update e2e tests in
Shipwright side. This story is almost complete, is only the private git tests missing.
For [2]. This should be in the release. Im trying to finish this today/tomorrow, then I
will ask for reviews. I might be blocked by the ongoing issues with [9].
For [3], plus one on pushing it into the upcoming release.
For [4], yes it can be postponed in my opinion. I think this one is very small CI item,
but I dont think we have time for this, this week. Its not that critical for now, it will
make the "Try It" section easier.
For [5]/[6], I think so far is ok, we should merge Jason´s PR
https://github.com/shipwright-io/build/pull/687 today/tomorrow. I can review also this one
.
For [7], this is a question for @Jordan, to see if we can deliver this week.
For [8|, I´m fine to do this in the next release.
[9] I think images in quay.io cannot be pulled (authentication is needed), so if we want
to publish a release, users will not be able to operate on the assets. We need to fix
this.
Regards,
Enrique E. Encalada