[Issue_678] Add missing category attributes #679
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
stability-level/community
github-actions
bot
added
stability-level/community
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #678
I also did a bit of light copy editing as I went along. A non-obvious one is removing the brackets from "[WFxxx-xxxx]" in the proposal titles, which is for aesthetic reasons. We now auto-add [PREVIEW] etc and I find two different uses of bracketed text to be ugly / confusing.
With this I see only 4 uncategorized items left:
Two that we should work out how to exclude from the landing page -- the feature process doc and the proposal template.
Two others that are validly not in any of our categories and don't deserve a category of their own. MR jars in jboss-parent and the user BOM source code move.