1:51 p.m.
*Open Issues*
1. Organize Samples - there was a request to add a private repo for end to
end testing [1]. If there are no objections, I would like to split this
into a separate issue. In addition to the private repo, we would need to
create and securely share CI bot credentials amongst project maintainers.
2. Reorganize README - in progress [2], this should merge before the
release.
3. Add contextDir to s2i - in progress [3], would be nice to fix before the
release.
4. Enhance CI for shipping releases - there was a request to include a
samples YAML manifest in our releases [4]. If we otherwise feel ready to
release, I think we can split this into a separate issue to be addressed in
v0.5.0.
5. API review of v1alpha1 - I have updated the issue to reflect our current
state [5]. The PR to unify our go and YAML object names feels like the last
of the API changes to be considered in this release [6] - are we missing
anything?
*Open PRs*
The following PRs that are not work in progress and are not enhancement
proposals:
1. Switch default branch to main [7] - any objections to merging this
before we release?
2. Unify Go struct and YAML/JSON field names [6] - see above.
3. Remote artifacts [8] - currently under review. Given this is a
significant new feature, I think this should wait until after the release
for merge. Any objections?
Please let me know if there are any additional open issues or PRs which
should be included in the next release.
Thank You,
Adam
[1] https://github.com/shipwright-io/build/issues/366#issuecomment-795535081
[2] https://github.com/shipwright-io/build/issues/655
[3] https://github.com/shipwright-io/build/issues/638
[4] https://github.com/shipwright-io/build/issues/574#issuecomment-795468753
[5] https://github.com/shipwright-io/build/issues/516
[6] https://github.com/shipwright-io/build/pull/687
[7] https://github.com/shipwright-io/build/pull/671
[8] https://github.com/shipwright-io/build/pull/616
--
Adam Kaplan
He/Him
Principal Software Engineer
Red Hat <https://www.redhat.com>
100 E. Davie Street
adam.kaplan(a)redhat.com T: 1-919-754-4843
<https://www.redhat.com>
4: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
1123
days inactive
1124
days old
shipwright-dev@lists.shipwright.io
1 comments
2 participants
participants (2)
-
Adam Kaplan -
Enrique Encalada