nova-specs/42a7a8660867cb49dc8ab23979e...

56 lines
2.1 KiB
Plaintext

{
"comments": [
{
"key": {
"uuid": "AAAAWH/+Jmc\u003d",
"filename": "specs/juno/backportable-db-migrations-juno.rst",
"patchSetId": 3
},
"lineNbr": 15,
"author": {
"id": 782
},
"writtenOn": "2014-03-28T19:23:03Z",
"side": 1,
"message": "This does suck for small blueprints. Lots of sections with the same text in...\n\nbut it does work I guess.",
"revId": "42a7a8660867cb49dc8ab23979ed6d429c777928",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "AAAAWH/+KYI\u003d",
"filename": "specs/juno/backportable-db-migrations-juno.rst",
"patchSetId": 3
},
"lineNbr": 88,
"author": {
"id": 1501
},
"writtenOn": "2014-03-28T17:50:29Z",
"side": 1,
"message": "I think the onus here has to be on the developer doing the backport, not the developer of the migration who has only a limited view of if it might be back ported.",
"revId": "42a7a8660867cb49dc8ab23979ed6d429c777928",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
},
{
"key": {
"uuid": "AAAAWH/+JeQ\u003d",
"filename": "specs/juno/backportable-db-migrations-juno.rst",
"patchSetId": 3
},
"lineNbr": 88,
"author": {
"id": 4393
},
"writtenOn": "2014-03-28T19:39:49Z",
"side": 1,
"message": "We can\u0027t really do that, unless the backporter makes corrections to the migration in master to make it idempotent, right? While possible, we generally try to avoid making changes (especially ones that may significantly change the behavior) once a migration is in the tree.\n\nSo far, we\u0027ve not had to do this, but I expect that when we do, it will be in a case where we\u0027re very aware of the fact that we need to backport it ahead of time.",
"parentUuid": "AAAAWH/+KYI\u003d",
"revId": "42a7a8660867cb49dc8ab23979ed6d429c777928",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543",
"unresolved": false
}
]
}