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

Update template and checks #581

Merged
merged 4 commits into from
Oct 10, 2024

Conversation

jmesnil
Copy link
Member

@jmesnil jmesnil commented Jun 27, 2024

  • Update the template to move the tracking issue and the stability level to the front matter
  • When a PR is open, check that these fields are valid
  • Generate a HTML page for the proposal with these fields.

This PR updates the template to be more descriptive about its expected content.

As a demo, I opened a "dummy" proposal in my fork that was missing the issue and stability-level in the front matter:

Before that PR is merged, the following labels must be created:

  • missing-issue - The analysis document is missing an issue tracker in its metadata
  • invalid-stability-level - The analysis document is missing a valid stability level in its metadata
  • stability-level/experimental - Feature is at the "Experimental" stability level
  • stability-level/preview - Feature is at the "Preview" stability level
  • stability-level/community - Feature is at the "Community" stability level
  • stability-level/default - Feature is at the "Default" stability level

@jmesnil jmesnil force-pushed the issue_stability_level_checks branch from af28396 to 98c4b6c Compare June 27, 2024 09:48
design-doc-template.adoc Outdated Show resolved Hide resolved
design-doc-template.adoc Outdated Show resolved Hide resolved
design-doc-template.adoc Outdated Show resolved Hide resolved
design-doc-template.adoc Outdated Show resolved Hide resolved
design-doc-template.adoc Outdated Show resolved Hide resolved
design-doc-template.adoc Outdated Show resolved Hide resolved
design-doc-template.adoc Outdated Show resolved Hide resolved
design-doc-template.adoc Outdated Show resolved Hide resolved
@jmesnil jmesnil force-pushed the issue_stability_level_checks branch from 98c4b6c to 0824288 Compare July 3, 2024 12:11
@jmesnil jmesnil force-pushed the issue_stability_level_checks branch 5 times, most recently from bd003b7 to 7822862 Compare September 17, 2024 07:40
* Update the template to move the tracking issue and the stability level to the front matter
* When a PR is open, check that these fields are valid
* Generate a HTML page for the proposal with these fields.

Signed-off-by: Jeff Mesnil <[email protected]>
Based on the value of the `stability-level` field in the front matter,
add a label `stability-level/xxx` to the PR.

Signed-off-by: Jeff Mesnil <[email protected]>
Copy link
Contributor

@bstansberry bstansberry left a comment

Choose a reason for hiding this comment

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

Hi @jmesnil -- I have a couple requests.

For context around these requests please have a look at https://docs.google.com/document/d/1e2hCAb--ApK32fPbUTWQSn6fH9GqmqZuaUPYwIp01JQ/edit. That's a draft of an email I plan to send to wildfly-dev once we merge this.

design-doc-template.adoc Outdated Show resolved Hide resolved
design-doc-template.adoc Show resolved Hide resolved
@bstansberry bstansberry mentioned this pull request Sep 30, 2024
_layouts/proposal.html Show resolved Hide resolved
* bring back Related Issues sections
* clarify the issue metadata semantic

Signed-off-by: Jeff Mesnil <[email protected]>
@jmesnil
Copy link
Member Author

jmesnil commented Oct 4, 2024

@bstansberry I've updated the PR and made some suggestions to the mail you will send. thanks!

@jmesnil
Copy link
Member Author

jmesnil commented Oct 4, 2024

I've created the labels that will be added to the PR based on their stability-level attributes:

  • stability-level/experimental
  • stability-level/preview
  • stability-level/community
  • stability-level/default

@jmesnil
Copy link
Member Author

jmesnil commented Oct 4, 2024

@bstansberry Could we also merge #584? It would unclutter the PR queue.
That would close 56 of 85 PR that have not been updated for the last 4 months (https://github.com/wildfly/wildfly-proposals/pulls?q=is%3Apr+updated%3A%3C2024-06-06+is%3Aopen)

@bstansberry bstansberry merged commit b59832a into wildfly:main Oct 10, 2024
1 check passed
@bstansberry
Copy link
Contributor

Thanks @jmesnil

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.

2 participants