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
