Update labels

Project-management.md

@@ -6,16 +6,25 @@ Labels track rough areas of concern or types of issues. Labels are defined as `<
 
 Current categories:
 
-- `area` The area in the game that this issue relates to
+- `area` The area in the game that the issue relates to
+- `platform` The operating system that the issue can be reproduced on
+- `priority` The importance of an issue that the core team should address before a release
+- `ruleset` The ruleset that the issue relates to
+- `size` (with a slash) The ranking of lines of code that a PR changes
 - `type` The type of an issue, if it can be defined into a common type
 
-We also have special labels for other use cases
+We also have special labels for other use cases:
 
 - `blocked` An issue which is blocked on another task or external fix.
-- `bounty` An issue which has a monetary bounty attached.
-- `good first issue` A good place to start contributing to this project without going too deep.
-- `low priority` A task which the core team will not address in the next 6 months. External contributors are welcome to attempt these tasks.
-- `proposal` An issue which has not yet reached consensus as to whether it will be implemented.
+- `compatibility-change` Changes to be considered in the future which break compatibility with osu!stable scores.
+- `dependencies` Pull requests that update a dependency file
+- `epic` A feature of core importance (and also requiring considerable effort and thought).
+- `framework-fix-required` An issue that can't be resolved without changes to osu!framework.
+- `good-first-issue` A good place to start contributing to this project without going too deep.
+- `missing-details` Can't move forward without more details from the reporter
+- `.NET` Pull requests that update .net code
+- `new-renderer` Will be fixed (or revisited) after veldrid / directx / vulkan come online.
+- `next-release` Pull requests which are almost there. We'll aim to get them in the next release, but no guarantees! 
 
 ## Projects