Update patch set 7

Patch Set 7:

(2 comments)

Patch-set: 7
Attention: {"person_ident":"Gerrit User 2271 \u003c2271@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_2271\u003e replied on the change"}
Attention: {"person_ident":"Gerrit User 11604 \u003c11604@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_2271\u003e replied on the change"}
This commit is contained in:
Gerrit User 2271 2024-04-08 04:38:27 +00:00 committed by Gerrit Code Review
parent b5d0fe1382
commit f8069bd753
1 changed files with 36 additions and 0 deletions

View File

@ -35,6 +35,24 @@
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "23d9761b_844b089b",
"filename": "specs/2024.2/approved/update-userdata.rst",
"patchSetId": 7
},
"lineNbr": 48,
"author": {
"id": 2271
},
"writtenOn": "2024-04-08T04:38:27Z",
"side": 1,
"message": "Its also possible to read this metadata with something other than cloud-init, but the reality is that _most_ people simply use cloud-init. I think if we\u0027re going to add things which can change post first boot, it would also be reasonable to ask if the cloud-init team has been consulted or informed of the plan.",
"parentUuid": "d0580207_6ba29bc9",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
@ -69,6 +87,24 @@
"parentUuid": "0e2a0a6d_40a4684e",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "e4c67c1a_5aa94712",
"filename": "specs/2024.2/approved/update-userdata.rst",
"patchSetId": 7
},
"lineNbr": 66,
"author": {
"id": 2271
},
"writtenOn": "2024-04-08T04:38:27Z",
"side": 1,
"message": "Here are the previous versions:\n\nFOLSOM \u003d \u00272012-08-10\u0027\nGRIZZLY \u003d \u00272013-04-04\u0027\nHAVANA \u003d \u00272013-10-17\u0027\nLIBERTY \u003d \u00272015-10-15\u0027\nNEWTON_ONE \u003d \u00272016-06-30\u0027\nNEWTON_TWO \u003d \u00272016-10-06\u0027\nOCATA \u003d \u00272017-02-22\u0027\nROCKY \u003d \u00272018-08-27\u0027\nVICTORIA \u003d \u00272020-10-14\u0027\n\nWe certainly _used_ to bump the version when we changed something. I don\u0027t see any changes since commit 916ffddca8d41daa367cf819e14827cf4b4180a5 (when the Victoria version was added) that weren\u0027t internal only with the exception of perhaps 1bf45c47205057801129dc20153de0a98d9c4e08.\n\nThat is, these have previously been versioned. Maybe one change has escaped versioning, but that doesn\u0027t seem like a strong reason to give up on versioning entirely.",
"parentUuid": "a5c92e0a_85d1217e",
"revId": "8162e70bd3b15f6ba34b5c661f867480df71ca76",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
}
]
}