Remove the priority field in v2
The priority field for MX and SRV records will no longer be a separate field in v2. Instead the priority will be placed at the beginning of the data field for MX and SRV records. In v1, it will continue to be displayed as a separate field. There will be no changes made to the database as a result of this blueprint. See Whiteboard below for example.
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- High
- Drafter:
- Betsy Luzader
- Direction:
- Approved
- Assignee:
- Betsy Luzader
- Definition:
- Approved
- Series goal:
- Accepted for juno
- Implementation:
-
Implemented
- Milestone target:
-
2014.2
- Started by
- Betsy Luzader
- Completed by
- Betsy Luzader
Related branches
Related bugs
Sprints
Whiteboard
Example of v1 SRV record:
{
"name": "_sip._
"type": "SRV",
"data": "0 5060 sip.example.com."
"priority": 30
}
Example of what it will look like in v2 after this change:
{
"recordset":{
"name"
"type":"SRV"
"records":[
"30 0 5060 sip.example3.com."
]
}
}
Gerrit topic: https:/
Addressed by: https:/
Remove the Priority Field in V2
