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

MMTk Enhancement Proposal #1056

Merged
merged 3 commits into from
Dec 22, 2023
Merged

MMTk Enhancement Proposal #1056

merged 3 commits into from
Dec 22, 2023

Conversation

wks
Copy link
Collaborator

@wks wks commented Dec 21, 2023

This PR adds a document that describes the MMTk Enhancement Proposal (MEP).

Copy link
Member

@qinsoon qinsoon left a comment

Choose a reason for hiding this comment

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

We probably want to put this doc in a separate folder under docs. This doc is not only for the team, but also for any developers. We could have a folder docs/contribute, and put the doc in the folder.

A check list before this PR is merged:

  • An issue template for MEP
  • An issue template for normal issues (optional)
  • Issue tags MEP and F-request-for-MEP.

docs/team/mep.md Outdated Show resolved Hide resolved
docs/team/mep.md Outdated Show resolved Hide resolved
docs/team/mep.md Outdated Show resolved Hide resolved
docs/team/mep.md Outdated
public API changes usually indicate such risks, but these are only indicators, not criteria. The
assessment of risks is subjective, and we need to discuss in order to reach consensus.

Note: JEP is also required for things that "require two or more weeks of engineering effort" and/or
Copy link
Member

Choose a reason for hiding this comment

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

I would suggest not mentioning too much about JEP, especially when it is irrelevant. 1. As you said, MEP is clearly different from JEP. 2. Not many people are that familiar with JEP so it is hard for them to draw connection between the two.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I agree. I removed all places that mention JEP, keeping only one sentence that mentions that MEP is inspired by JEP.

docs/team/mep.md Outdated Show resolved Hide resolved
docs/team/mep.md Outdated Show resolved Hide resolved
docs/team/mep.md Outdated Show resolved Hide resolved
docs/team/mep.md Outdated Show resolved Hide resolved
docs/team/mep.md Outdated Show resolved Hide resolved
docs/team/mep.md Outdated Show resolved Hide resolved
Copy link
Member

@qinsoon qinsoon left a comment

Choose a reason for hiding this comment

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

LGTM

@wks wks added this pull request to the merge queue Dec 22, 2023
Merged via the queue into mmtk:master with commit 0fb1acf Dec 22, 2023
19 checks passed
@wks wks deleted the feature/mep branch December 22, 2023 05:47
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