mirror of
https://gitlab.isc.org/isc-projects/kea
synced 2025-08-29 13:07:50 +00:00
Update gitlab howto
parent
e019774ba7
commit
a239da55b6
@ -91,4 +91,19 @@ When migrating stuff between repos, DO NOT copy files over. Use cherry-pick inst
|
||||
|
||||
**Registration for users is working**.
|
||||
|
||||
**We are yet to experience the power of CI**. There will be screams in the process and tears of joy at the end.
|
||||
**We are yet to experience the power of CI**. There will be screams in the process and tears of joy at the end.
|
||||
|
||||
# Using labels
|
||||
One major difference,advantage or a flaw (depending on your personal preference) of gitlab is its label system.
|
||||
|
||||
Violet labels are for priority. There are four priority labels: critical, high, medium and low.
|
||||
|
||||
Orange labels are for components.
|
||||
|
||||
Green labels designate type and state of the issue (feature request, QA needed, etc)
|
||||
|
||||
Yellow labels designate specific libraries.
|
||||
|
||||
Red labels are for things that should stand out. Currently there's one label: bug.
|
||||
|
||||
This is just a proposal. Tomek's idea was to use dark colors for important things and light colors for less important aspects. If you don't like it, we can come up with an alternative naming/coloring scheme.
|
||||
|
Loading…
x
Reference in New Issue
Block a user