forked from grizz/ghmeta
-
Notifications
You must be signed in to change notification settings - Fork 1
/
data.yml
75 lines (75 loc) · 2.3 KB
/
data.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
ghmeta:
push_to:
- peeringdb/peeringdb
- peeringdb/peeringdb-py
- peeringdb/django-peeringdb
labels:
- color: fbca04
description: Admin Committee
name: AC
- color: 0052cc
description: Issues cannot be completed until another issue is done
name: Blocked
- color: fbca04
description: null
name: Board
- color: c2e0c6
description: Data Ownership TF related issue
name: Data Ownership TF
- color: c2e0c6
description: More than 10 hours work
name: Hourly
- color: c2e0c6
description: 4 - 10 hours work
name: Major
- color: c2e0c6
description: Up to 4 hours
name: Minor
- color: 0052cc
description: Fixing the issue will not require touching the code
name: No code change
- color: fbca04
description: Operations Committee
name: Operations
- color: fbca04
description: Outreach Committee
name: Outreach
- color: c2e0c6
description: ''
name: Quote
- color: ffa500
description: Implementing this ticket requires user be notified
name: Requires Notice
- color: ee0701
description: null
name: bug
- color: 84b6eb
description: null
name: enhancement
- color: e6e6e6
description: null
name: invalid
- color: 304cc9
description: ''
name: translations
milestones:
- description: "Issues under Decide queue. \r\nIssues are kept in Decide while the\
\ Product Committee discusses the issue. \r\nNext milestone is \"Consensus Reached\""
title: 1 Decide
- description: "Issues that are in the Consensus queue.\r\nWhen a decision is made\
\ about how an issue will be dealt with by the Product Committee, the issue is\
\ moved to \"Consensus Reached\"\r\nNext milestone is \"Consensus Finalized\"\r\
\nPrevious milestone is \"Decide\""
title: 2 Consensus Reached
- description: "When an issue is at milestone \"Consensus reached\" PC members have\
\ the opportunity to oppose for five days. If no one objects the issue is moved\
\ forward to Consensus Finalized.\r\nIssues here wait for implementation details\
\ fo be sorted out.\r\nThe next milestone is \"Implementation Discussion\""
title: 3 Consensus Finalized
- description: 'Last milestone before milestone "Next release". The predecessor is
"Consensus Finalized". '
title: 4 Ready for Implementation
- description: ''
title: 3a Needs Implementation discussion
- description: ''
title: Next Release