openstack
/
project-team-guide
Code Issues Proposed changes

Update patch set 1 

Patch Set 1:

(1 comment)

Patch-set: 1
Attention: {"person_ident":"Gerrit User 17685 \u003c17685@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"ADD","reason":"\u003cGERRIT_ACCOUNT_11904\u003e replied on the change"}
Attention: {"person_ident":"Gerrit User 11904 \u003c11904@4a232e18-c5a9-48ee-94c0-e04e7cca6543\u003e","operation":"REMOVE","reason":"\u003cGERRIT_ACCOUNT_11904\u003e replied on the change"}
This commit is contained in:
Gerrit User 11904 2024-05-17 14:32:54 +00:00 committed by Gerrit Code Review
parent ebaa228d2c
commit ad14140207
1 changed files with 18 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
b599e7dbb534ef5867b8d5546dc355a1616a4d10
View File

@ -69,6 +69,24 @@
"revId": "b599e7dbb534ef5867b8d5546dc355a1616a4d10",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "daf238ef_a5d4efec",
"filename": "doc/source/repository.rst",
"patchSetId": 1
},
"lineNbr": 161,
"author": {
"id": 11904
},
"writtenOn": "2024-05-17T14:32:54Z",
"side": 1,
"message": "Ah, you\u0027re right. I had to remember how we did EOL in the past.\n\nEOL should be on the last commit, not the last release. It\u0027s a marker to say \"nothing more is expected past this point.\" So there could be the last release, but it\u0027s possible the project merged changes since then. The last release is different than when the stable branch went end of life. They may choose to do one final release, in which has EOL would be the same as the last release tag. But I think often times there are changes that are merged that don\u0027t need a new release, so the EOL tag just indicates the point in that branch where any further work is cut off.",
"parentUuid": "6a7d69fc_a84b41fc",
"revId": "b599e7dbb534ef5867b8d5546dc355a1616a4d10",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {