Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add EP template and first EP #4

Open
wants to merge 10 commits into
base: master
Choose a base branch
from

Conversation

vitus133
Copy link
Contributor

This commit adds the enhancement proposal directory structure and template. It also adds a sample enhancement proposal for API unification
/cc @josephdrichard @aneeshkp


```yaml
e810:
internalDelays:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prefer spaces over tabs for yaml indentation

@josephdrichard josephdrichard force-pushed the master branch 2 times, most recently from 6cf3a30 to ab4968d Compare January 29, 2025 05:57
COPY bindata /bindata

LABEL io.k8s.display-name="OpenShift ptp-operator" \
io.k8s.description="This is a component that manages cluster PTP configuration." \
io.openshift.tags="openshift,ptp" \
com.redhat.delivery.appregistry=true \
maintainer="PTP Dev Team <ptp[email protected]>"
maintainer="Multus Team <multus[email protected]>"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be
maintainer="PTP Dev Team [email protected]"

@@ -1,12 +1,12 @@
FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.18 AS builder
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not sure if we are running ci using rhel images or now . Any comment on this ? Do we have CI integrated for upstream now


ENTRYPOINT ["/usr/local/bin/ptp-operator"]
ENTRYPOINT ["/usr/local/bin/ptp-operator"]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

return char

@@ -9,7 +9,7 @@ reviewers:
- SchSeba
- fedepaol
- oribon
- josephdrichard
- k8snetworkplumbingwg
- aneeshkp
- nishant-parekh
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we can remove everyone that are not valid here

@@ -9,7 +9,7 @@ reviewers:
- SchSeba
- fedepaol
- oribon
- josephdrichard
- k8snetworkplumbingwg
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also why joseph removed?

@@ -24,7 +24,7 @@ approvers:
- SchSeba
- fedepaol
- oribon
- josephdrichard
- k8snetworkplumbingwg
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also why joseph removed?

@@ -1,12 +1,12 @@
FROM registry.ci.openshift.org/ocp/builder:rhel-9-golang-1.22-openshift-4.18 AS builder
WORKDIR /go/src/github.com/openshift/ptp-operator
WORKDIR /go/src/github.com/k8snetworkplumbingwg/ptp-operator
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

o we need ocp dockerfile upstream ?

@@ -0,0 +1,30 @@
# Regression testing
Regressions will be run periodically by QE, in order to ensure that everything is functional. This should be done before every release, including new builds of previous releases. Nothing should be delivered to customers that QE hasn't run a regression on and signed off on.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Who is upstream QE here ? our upstream CI should be configured to run regression ., I don't think QE will be running any regression on upstream

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants