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

Create feature-lifecycle-and-deprecation #193

Merged
merged 5 commits into from
Jul 12, 2022
Merged

Create feature-lifecycle-and-deprecation #193

merged 5 commits into from
Jul 12, 2022

Conversation

qnetter
Copy link
Contributor

@qnetter qnetter commented Apr 21, 2022

Policy proposal for community preview.

Copy link
Member

@Vad1mo Vad1mo left a comment

Choose a reason for hiding this comment

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

good idea

Copy link
Contributor

@wy65701436 wy65701436 left a comment

Choose a reason for hiding this comment

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

lgtm


Once the issue is filed, a discussion period begins which ends at the beginning of the second community meeting after the opening of the issue, and is held at the community meeting and on the issue itself; the person who opens the issue or a maintainer should add that date and time in a comment in the issue as soon after the issue is opened as possible.

The feature will be deprecated by a supermajority vote of 50% plus one of the project maintainers at the time of the vote tallying, which is 72 hours after the end of the community meeting that is the end of the comment period. (Maintainers are permitted to vote in advance of the deadline, but should hold their votes until as close as possible to hear all possible discussion.) Votes will be tallied in comments on the issue.
Copy link
Member

Choose a reason for hiding this comment

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

How we are going to track that timing?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

How we are going to track that timing?

We can track in deprecation issue comments and meeting minutes. Issue comments should be authoritative.

Copy link
Member

@OrlinVasilev OrlinVasilev left a comment

Choose a reason for hiding this comment

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

lgtm

@OrlinVasilev
Copy link
Member

looks great to me
BTW @qnetter I have enabled DCO(signing) from web interface for that repository and website can you give it a try ?

Thanks

@OrlinVasilev OrlinVasilev self-assigned this Jul 12, 2022
@qnetter qnetter requested review from a team as code owners July 12, 2022 16:41
@qnetter
Copy link
Contributor Author

qnetter commented Jul 12, 2022

looks great to me BTW @qnetter I have enabled DCO(signing) from web interface for that repository and website can you give it a try ?

Thanks

Done.

@Vad1mo Vad1mo merged commit aab4e93 into main Jul 12, 2022
@qnetter qnetter deleted the qnetter-patch-1 branch July 14, 2022 00:23
@qnetter
Copy link
Contributor Author

qnetter commented Jul 14, 2022

So please note that the voting period is already underway, and people should comment on this issue with +1 (and any comments) to approve, 0 to neither approve nor disapprove, or -1 to disapprove; non-maintainers should add "nb" for non-binding (though of course we know who the maintainers are). Votes will be tallied at the next community meeting. @OrlinVasilev please comment with that date/time below. @goharbor/all-maintainers please vote.

@OrlinVasilev
Copy link
Member

OrlinVasilev commented Jul 14, 2022

June 13th 23:59 UTC!
BTW @qnetter not sure commenting the time stamp will be doable but let's try :)

@qnetter
Copy link
Contributor Author

qnetter commented Aug 17, 2022

Completed.

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.

4 participants