| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Update repository handling document https://review.opendev.org/c/openstack/project-team-guide/+/836111 | 03:18 |
|---|---|---|
| *** Guest318 is now known as diablo_rojo_phone | 04:06 | |
| *** diablo_rojo_phone is now known as diablo_rojo | 04:10 | |
| *** akahat is now known as akahat|rover | 06:35 | |
| *** pojadhav- is now known as pojadhav | 08:13 | |
| *** pojadhav- is now known as pojadhav | 12:18 | |
| gmann | jungleboyj: I am preparing the schedule for TC PTG slots, are you ready with user survey things? and roughly how much time it will take? | 17:16 |
| gmann | ade_lee: is Thursday 14-15 UTC ok for you for FIPs goal? | 17:21 |
| ade_lee | gmann, I was just thinking about this -- checking | 17:22 |
| ade_lee | gmann, no sorry - I'll be meeting with glance then about fips | 17:23 |
| gmann | ade_lee: ok, what time best for you on Thursday/Friday | 17:24 |
| ade_lee | gmann, checking | 17:24 |
| ade_lee | gmann, 15-16 utc thurs? | 17:29 |
| ade_lee | gmann, really any time on thurs after 9:15 am EDT -- ie: 13:15 except for 14-15 | 17:31 |
| ade_lee | gmann, ditto for friday | 17:32 |
| gmann | ade_lee: done on Thursday 15-16 https://etherpad.opendev.org/p/tc-zed-ptg#L89 | 17:32 |
| ade_lee | gmann, cool thanks | 17:32 |
| ade_lee | gmann, ah sorry for confusion - when I put in those updates in the etherpad before I just did a conversion from edt instead of thinking in utc. and of course, the time changed for utc since then | 17:35 |
| gmann | ade_lee: no issue, I am still preparing it so we can change | 17:36 |
| ade_lee | gmann, no worries - the time we selected is good now | 17:36 |
| gmann | cool. | 17:36 |
| ade_lee | gmann, sorry actually ... I just realized glance is from 15-15:35 utc -- so what you asked for initially is better | 17:40 |
| ade_lee | gmann, 14-15 utc | 17:40 |
| ade_lee | aargh, time zones .. | 17:40 |
| gmann | ok, 14-15 UTC Thursday final? | 17:41 |
| ade_lee | yup - sorry for (my) confusion | 17:41 |
| gmann | ok, np at all | 17:41 |
| gmann | tc-members: I have preapred the rough schedule, please let me know if any of your topic/interested to join need re-scheduling https://etherpad.opendev.org/p/tc-zed-ptg | 17:49 |
| gmann | tc-members: need 2nd review in these project-team-guide changes https://review.opendev.org/q/project:openstack/project-team-guide+status:open+owner:gmann%2540ghanshyammann.com | 18:55 |
| dansmith | gmann: schedule looks fine to me, btw | 19:11 |
| gmann | ok | 19:11 |
| dansmith | gmann: you want me to +W that reorg or do we need more votes? | 19:12 |
| dansmith | mine were merged with just two so I assume I'm good | 19:12 |
| gmann | dansmith: yeah, in project-team-guide we just need normal code review, two +2. TC motion are not applicable to this repo. | 19:13 |
| opendevreview | Merged openstack/governance master: Define 2022 upstream investment opportunities https://review.opendev.org/c/openstack/governance/+/835166 | 19:14 |
| dansmith | gmann: did you see the comments on this one? https://review.opendev.org/c/openstack/project-team-guide/+/834796 | 19:16 |
| gmann | dansmith: ah no, checking | 19:17 |
| gmann | updating | 19:18 |
| dansmith | also a couple grammar nits on the bottom patch | 19:18 |
| dansmith | I would have fixed in place, but figured you'd be revising the one above anyway | 19:18 |
| dansmith | gmann: ^ | 19:18 |
| gmann | dansmith: ack, thanks. updating | 19:18 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Modify the project specific stable team management https://review.opendev.org/c/openstack/project-team-guide/+/834794 | 19:21 |
| opendevreview | Merged openstack/project-team-guide master: Move technical-guidance.rst under technical-guides https://review.opendev.org/c/openstack/project-team-guide/+/834803 | 19:21 |
| opendevreview | Merged openstack/project-team-guide master: Update repository handling document https://review.opendev.org/c/openstack/project-team-guide/+/836111 | 19:21 |
| rosmaita | gmann: left a question for you on https://review.opendev.org/c/openstack/project-team-guide/+/834794 | 19:26 |
| dansmith | rosmaita: you reviewed PS1 by the way | 19:27 |
| rosmaita | yeah, but when i started, that was the only ps there | 19:27 |
| dansmith | rosmaita: yeah, sorry, just pointing out that your group comment is resolved I think by the s/that/those/ | 19:28 |
| gmann | checking | 19:28 |
| rosmaita | yes, but the important part was whether "core" is correct there or not | 19:28 |
| dansmith | yep | 19:29 |
| dansmith | core is the right term, IMHO, | 19:29 |
| dansmith | and doesn't need to be the same as a core on the master branch | 19:29 |
| gmann | yeah it is mentioned as 'Stable Branch core' | 19:29 |
| gmann | which can be anyone even who is not core in master | 19:30 |
| rosmaita | well, my point is that person doesn | 19:30 |
| dansmith | stable-maint-core | 19:30 |
| rosmaita | 't necessarily have to be stable-maint-core | 19:30 |
| dansmith | is one of the main group names in gerrit | 19:30 |
| rosmaita | i will go reread, maybe i missed the point there | 19:31 |
| dansmith | maybe I'm not understanding the problem | 19:31 |
| dansmith | "the project stable branch core" means "someone with +2 on the stable branches for that project" and nothing more (to me) | 19:32 |
| dansmith | not core on master, not stable-maint-core | 19:32 |
| gmann | how about naming them as "Projects Stable Maintenance teams" and "Central Stable Maintenance Team" | 19:34 |
| gmann | or this can be more confusing if changing the existing team name. so what do i need t clarify in that? | 19:36 |
| fungi | is there still any (viable) central stable-maint team? | 19:36 |
| rosmaita | gmann: don't change any names! | 19:36 |
| gmann | yeah elodilles is there | 19:36 |
| gmann | rosmaita: yeah | 19:36 |
| gmann | so updating two comments? 1. 'that group' and 2. 'consult on' | 19:39 |
| rosmaita | my problem is that the sentence you revised addressed the question of where the {project}-stable-maint comes from; originally it was the stable branch x-p liasion + stable-maint-core, and then others added with approval of the {project}-stable-maint. Now it assumes the existence of a project Stable Branch core team | 19:39 |
| rosmaita | but the question is, where did that project Stable Branch core team come from? | 19:39 |
| dansmith | it says in there that it's a group managed by the project itself right? | 19:41 |
| dansmith | like the main core team | 19:41 |
| gmann | L192/193 "Each project with a stable branch will have a project-specific stable | 19:41 |
| gmann | maintenance Gerrit team called PROJECTNAME-stable-maint. " | 19:41 |
| gmann | initial lines in that para explain about project stable branch core team. I can use the same same to make it easy - "That group should be the PROJECTNAME-stable-maint + the stable maintenance core team. That group is....." | 19:43 |
| gmann | *same name | 19:43 |
| gmann | "That group should be the PROJECTNAME-stable-maint team + the stable maintenance core team. That group is....." | 19:44 |
| gmann | rosmaita: dansmith ^^ it is fine? | 19:44 |
| rosmaita | gmann: works for me | 19:45 |
| dansmith | yeah, I'm not sure what the problem with it is right now, tbh, but I think that proposed line just puts the word "core" in the first sentence to tie them together, is that right? | 19:45 |
| dansmith | if so, then sure | 19:45 |
| gmann | ohk, I think I end up it weird. this line explain who is in 'PROJECTNAME-stable-maint team ' group and adding same group name does not make sense. I think existing lines are correct | 19:50 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Modify the project specific stable team management https://review.opendev.org/c/openstack/project-team-guide/+/834794 | 20:00 |
| gmann | rosmaita: dansmith ^^ how about this | 20:00 |
| rosmaita | looking | 20:00 |
| rosmaita | i think that's good ... the whole point here is to change the role of the stable-maint-core from approving members of PROJECT-stable-maint to just having a consulting role | 20:05 |
| gmann | yes | 20:06 |
| gmann | project team can add/remove member from this group | 20:06 |
| rosmaita | ok | 20:07 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Modify the project specific stable team management https://review.opendev.org/c/openstack/project-team-guide/+/834794 | 20:09 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Modify the project specific stable team management https://review.opendev.org/c/openstack/project-team-guide/+/834794 | 20:11 |
| rosmaita | gmann: the difference between PS 4 and 5 is that the list of projects somehow sneaked back into 4, so you re-deleted it? | 20:14 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Move the projects list following the stable branch policy https://review.opendev.org/c/openstack/project-team-guide/+/834796 | 20:15 |
| gmann | rosmaita: I messed up my local branch with ^^ this review. now corrected both. | 20:15 |
| rosmaita | ok | 20:15 |
| gmann | rosmaita: dansmith : these both are ready now https://review.opendev.org/c/openstack/project-team-guide/+/834794/5 https://review.opendev.org/c/openstack/project-team-guide/+/834796/3 | 20:30 |
| rosmaita | gmann: you may be fixing this on a different patch somewhere, but i noticed that https://review.opendev.org/c/openstack/project-team-guide/+/834794/5/doc/source/stable-branches.rst#253 mentions the stable:follows-policy tag | 20:32 |
| gmann | rosmaita: let me fix it in https://review.opendev.org/c/openstack/project-team-guide/+/834796/ | 20:34 |
| rosmaita | sure | 20:34 |
| opendevreview | Ghanshyam proposed openstack/project-team-guide master: Move the projects list following the stable branch policy https://review.opendev.org/c/openstack/project-team-guide/+/834796 | 20:37 |
| gmann | rosmaita: ^^ done | 20:37 |
| rosmaita | fungi: if you're still around, how do projects get into the periodic-stable pipeline? | 21:25 |
| gmann | rosmaita: you mean this? https://opendev.org/openstack/openstack-zuul-jobs/src/branch/master/zuul.d/project-templates.yaml#L2201 | 21:28 |
| gmann | periodic-stable-jobs template is there in every project zuul.yaml file and run these doc and python unit test job on stable branch | 21:28 |
| rosmaita | gmann: thanks, that's what i was looking for | 21:30 |
| gmann | on every new stable branch cut, QA team add the new stable branch in that template as per the defined testing runtime of that release | 21:30 |
| fungi | rosmaita: yes, exactly what gmann said | 21:45 |
| fungi | lmk if you need more details | 21:45 |
| rosmaita | fungi: thanks, that's all i need | 21:45 |
| opendevreview | Brian Rosmaita proposed openstack/project-team-guide master: Update note about periodic jobs https://review.opendev.org/c/openstack/project-team-guide/+/836216 | 22:22 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!