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

monorepo labels draft #29

Merged
merged 18 commits into from
Aug 25, 2023
Merged

monorepo labels draft #29

merged 18 commits into from
Aug 25, 2023

Conversation

the-right-joyce
Copy link
Collaborator

@the-right-joyce the-right-joyce commented May 9, 2023

related to #25
this PR should serve solely to have a proposal and discussion about the new labels for the monorepo

this PR here should just serve to have a proposal and discussion about the new labels for the monorepo
color: 5319e7
- name: T9-polkadot
description: This PR/Issue is related to/affects Polkadot.
color: ffeeee
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

do we need to specify this here more? like: relay chain, collators, staking, etc.?

@juangirini
Copy link
Contributor

No Status nor Urgency labels 😍

Comment on lines 149 to 151
- name: I10-optimisation
description: An enhancement to provide better overall performance in terms of time-to-completion for a task.
color: c5def5
Copy link

Choose a reason for hiding this comment

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

I'd like to have two labels here: one for CPU optimization, and one for memory usage optimizations.

Copy link
Collaborator Author

@the-right-joyce the-right-joyce May 12, 2023

Choose a reason for hiding this comment

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

would it be enough if you use I10-optimisation with a T* label? Then I'd add there T12-CPU and T13-memory_usage? And you can then mix and match with other labels, like: bug, annoyance, etc.

@koute
Copy link

koute commented May 10, 2023

@the-right-joyce Are these labels only supposed to be for PRs, or also for the issues? I think it'd probably make sense to have separate sets of labels for both.

ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
changes based on comments:
b > breaking changes
c > complexity labels
f removed
A6 moved to I11
host function labels updated
deprecation label added
benchmark added
Copy link

@michalkucharczyk michalkucharczyk left a comment

Choose a reason for hiding this comment

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

looks good. left some nitpicks.

ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
@juangirini
Copy link
Contributor

@the-right-joyce Are these labels only supposed to be for PRs, or also for the issues? I think it'd probably make sense to have separate sets of labels for both.

I'd like to back up this idea, I think issues and prs are many times mixed up, and having different labels for those would be a great step into separating them

@the-right-joyce
Copy link
Collaborator Author

@juangirini we can define this with the ruled labels tool from @chevdor
A and B are def PR labels
C and I are issue labels
T is for both

- Delete D* labels
- Add RnD for Tax-Department
- Merge wont fix/invalid
ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
ruled_labels/[DRAFT]specs_monorepo.yaml Outdated Show resolved Hide resolved
@juangirini juangirini linked an issue May 23, 2023 that may be closed by this pull request
Copy link

@kianenigma kianenigma left a comment

Choose a reason for hiding this comment

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

Seems like we have no audit labels anymore. All good, but do we have a replacement system in mind?

@juangirini
Copy link
Contributor

Seems like we have no audit labels anymore. All good, but do we have a replacement system in mind?

We'll use a project to track audit issues #29 (comment)

Co-authored-by: Juan <juangirini@gmail.com>
@chevdor
Copy link
Contributor

chevdor commented May 30, 2023

We'll use a project to track...

Today, we are using the Audit labels to inform readers of the release notes about what has been audited, what does ont require aurditing, etc... Is it planned to drop this feature ?

@the-right-joyce
Copy link
Collaborator Author

yes

@the-right-joyce the-right-joyce linked an issue Jun 13, 2023 that may be closed by this pull request
@sam0x17
Copy link

sam0x17 commented Jun 15, 2023

@juangirini we can define this with the ruled labels tool from @chevdor A and B are def PR labels C and I are issue labels T is for both

for clarity, I would be in support of prefixing PR-related labels with PR- and issue-related labels with I-. That way you can just look down the list alphabetically and apply each category of label relevant to whether you are doing a PR or an issue and feel confident that you hit every category.

This doesn't help with the shared T labels but it will make everything else more clear

@bkchr
Copy link
Member

bkchr commented Jun 15, 2023

feel confident that you hit every category.

You are trying to workaround the fact that there are too many labels and they are not explained. This should hopefully not be the case anymore with these refactoring.

Copy link

@kianenigma kianenigma left a comment

Choose a reason for hiding this comment

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

In the mono-repo, I suggest we break the. T1-Runtime into two buckets:

T1-FRAME (changes to core frame, the framework, not a particular pallet)
T2-Pallets (changes to a particular pallet, possibly used by others)

for example now in PBA I want to report the latest changes in FRAME the framework to Shawn to update himself, but filtering by T1-Runtime is super noisy, contains million patches to random pallets that are unrelated to the FRAME itself.

@alvicsam alvicsam merged commit d8d716b into main Aug 25, 2023
5 checks passed
@alvicsam alvicsam deleted the the-right-joyce-monorepo-labels branch August 25, 2023 15:27
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.

Create new deprecation label Labels in the monorepo