44 lines
1.9 KiB
Plaintext
44 lines
1.9 KiB
Plaintext
{
|
|
"comments": [
|
|
{
|
|
"unresolved": true,
|
|
"key": {
|
|
"uuid": "32982b65_a63335f8",
|
|
"filename": "/PATCHSET_LEVEL",
|
|
"patchSetId": 1
|
|
},
|
|
"lineNbr": 0,
|
|
"author": {
|
|
"id": 32832
|
|
},
|
|
"writtenOn": "2024-01-15T05:41:31Z",
|
|
"side": 1,
|
|
"message": "Hi, Vefa and architects: \n I\u0027m fine with the spec. \n I have a question here which might be not necessary for the spec, but is important for our kernel developing process on this upgrading. From my work by now, I found this kernel upgrading can cause some user interface changes (e.g. attribute files change under proc/ sys/ ...) and they will cause jenkins installation failures. Those issues need to be solved or located by wrcp framework. Then it is a problem how kernel and framework work together. If we merge kernel first, it will cause broken installation. If we merge all the changes together, it will involve a mass of patches from different developers.\n Do you have any idea about how we deal with this? Will it be OK if we use a temp branch for those repos of this upgrading and merge them back when all the work finished?\n Thanks.",
|
|
"revId": "8d05288efa59f8bcf1e9230bb4e68e1abceb1268",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
|
},
|
|
{
|
|
"unresolved": false,
|
|
"key": {
|
|
"uuid": "682aa0e0_e25da0c8",
|
|
"filename": "doc/source/specs/stx-10.0/approved/os-2011000-uprevision-kernel-to-v6.6.rst",
|
|
"patchSetId": 1
|
|
},
|
|
"lineNbr": 264,
|
|
"author": {
|
|
"id": 32832
|
|
},
|
|
"writtenOn": "2024-01-15T05:41:31Z",
|
|
"side": 1,
|
|
"message": "we are expecting this spec for drivers.",
|
|
"range": {
|
|
"startLine": 262,
|
|
"startChar": 25,
|
|
"endLine": 264,
|
|
"endChar": 29
|
|
},
|
|
"revId": "8d05288efa59f8bcf1e9230bb4e68e1abceb1268",
|
|
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
|
|
}
|
|
]
|
|
} |