*** ianychoi__ is now known as ianychoi | 00:44 | |
openstackgerrit | Brian Rosmaita proposed openstack/releases master: Proposing victoria RC2 for cinder https://review.opendev.org/756599 | 01:35 |
---|---|---|
*** ricolin_ has joined #openstack-release | 01:45 | |
*** tkajinam has quit IRC | 01:52 | |
*** tkajinam has joined #openstack-release | 01:53 | |
*** armax has quit IRC | 03:26 | |
*** armstrong has quit IRC | 04:05 | |
*** evrardjp has quit IRC | 04:33 | |
*** evrardjp has joined #openstack-release | 04:33 | |
*** ykarel has joined #openstack-release | 04:55 | |
*** sboyron_ has joined #openstack-release | 05:40 | |
*** vishalmanchanda has joined #openstack-release | 06:54 | |
*** slaweq has joined #openstack-release | 07:01 | |
*** rpittau|afk is now known as rpittau | 07:27 | |
*** ttx has quit IRC | 07:33 | |
*** mgoddard has quit IRC | 07:36 | |
*** ttx has joined #openstack-release | 07:38 | |
*** mgoddard has joined #openstack-release | 07:39 | |
*** jtomasek_ has joined #openstack-release | 07:44 | |
*** jtomasek has quit IRC | 07:45 | |
*** tosky has joined #openstack-release | 07:54 | |
*** jtomasek_ has quit IRC | 07:56 | |
*** jtomasek has joined #openstack-release | 08:00 | |
*** e0ne has joined #openstack-release | 08:01 | |
*** ttx has quit IRC | 08:02 | |
*** ttx has joined #openstack-release | 08:02 | |
openstackgerrit | Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/releases master: Release OpenStack-Ansible Ussuri https://review.opendev.org/756656 | 08:30 |
openstackgerrit | Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/releases master: Release OpenStack-Ansible Train https://review.opendev.org/756657 | 08:32 |
openstackgerrit | Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/releases master: Release OpenStack-Ansible Ussuri https://review.opendev.org/756656 | 08:32 |
openstackgerrit | Dmitriy Rabotyagov (noonedeadpunk) proposed openstack/releases master: Release OpenStack-Ansible Stein https://review.opendev.org/756659 | 08:33 |
openstackgerrit | Merged openstack/releases master: Release Neutron RC2 for Victoria https://review.opendev.org/756582 | 08:49 |
openstackgerrit | Merged openstack/releases master: Proposing victoria RC2 for cinder https://review.opendev.org/756599 | 08:49 |
openstackgerrit | Merged openstack/releases master: Release octavia-dashboard 6.0.0rc2 https://review.opendev.org/756581 | 08:49 |
openstackgerrit | Merged openstack/releases master: Update final-rc process https://review.opendev.org/756053 | 09:00 |
*** dtantsur|afk is now known as dtantsur | 09:05 | |
*** sboyron_ is now known as sboyron | 09:07 | |
*** johnsom has quit IRC | 09:25 | |
*** johnsom has joined #openstack-release | 09:25 | |
*** armax has joined #openstack-release | 09:54 | |
*** jtomasek has joined #openstack-release | 11:58 | |
*** jtomasek_ has joined #openstack-release | 12:06 | |
*** jtomasek has quit IRC | 12:07 | |
*** armstrong has joined #openstack-release | 12:08 | |
openstackgerrit | Luigi Toscano proposed openstack/releases master: sahara: tag ocata as EOL https://review.opendev.org/756701 | 13:03 |
openstackgerrit | Luigi Toscano proposed openstack/releases master: sahara: tag pike as EOL https://review.opendev.org/756702 | 13:12 |
openstackgerrit | Luigi Toscano proposed openstack/releases master: sahara: tag pike as EOL https://review.opendev.org/756702 | 13:41 |
openstackgerrit | Merged openstack/releases master: Create stable/victoria branches for Puppet OpenStack https://review.opendev.org/756015 | 14:29 |
openstackgerrit | Merged openstack/releases master: Release OpenStack-Ansible Ussuri https://review.opendev.org/756656 | 14:33 |
openstackgerrit | Merged openstack/releases master: Release OpenStack-Ansible Train https://review.opendev.org/756657 | 14:36 |
openstackgerrit | Merged openstack/releases master: Release OpenStack-Ansible Stein https://review.opendev.org/756659 | 14:36 |
armstrong | Hello smcginnis | 14:37 |
*** slaweq has quit IRC | 14:38 | |
*** slaweq has joined #openstack-release | 14:42 | |
smcginnis | Hey armstrong. I just realized a little while ago that my days are all mixed up. I guess we should have proposed those patches yesterday. | 14:43 |
smcginnis | Totally felt like a Tuesday to me. :) | 14:43 |
smcginnis | armstrong: Is that something you can do now? | 14:44 |
hberaud | smcginnis, ttx: FYI I will likely missing a part of our meeting today | 14:45 |
smcginnis | hberaud: ack | 14:45 |
armstrong | Yes smcginnis | 14:53 |
armstrong | smcginnis: I ran the script few minutes ago and similar result like what we got yesterday | 14:54 |
smcginnis | armstrong: Yeah, I think there were just a couple of RC2 patches that went through since yesterday. So the list should be pretty close to the same. | 14:56 |
smcginnis | armstrong: Are you going to use new-release or process_auto_releases? You can also edit the files manually, but that's not the most efficient option. | 14:57 |
*** ykarel is now known as ykarel|away | 14:57 | |
armstrong | smcginnis: I prefer to use a script but have no particular preference. Since I haven't used any yet. | 14:59 |
*** priteau has joined #openstack-release | 14:59 | |
smcginnis | Then I think getting the list of repo names in a text file and using process_auto_releases is probably the most efficient. | 15:00 |
armstrong | smcginnis: however, it seems I need to output the result of the first command into a text file to create a list from there? Or how do we get the list you mentioned? | 15:00 |
smcginnis | armstrong: You can either pipe the output from the first command into a file and delete 99% of it, or just edit a text file and paste or type in each one that's needed. | 15:01 |
smcginnis | Since there were only a small number of repos that looked like they needed a new RC, might be easiest just copy/pasting from the command output into the file. | 15:02 |
smcginnis | But whatever works for you. | 15:02 |
armstrong | smcginnis: it seems each line of the output begins with : "[ Unreleased changes in openstack/ XX (stable/victoria) ]" | 15:03 |
smcginnis | Yes | 15:04 |
armstrong | smcginnis: so the name of the project in the XX, has not yet release right? | 15:04 |
armstrong | Smcginnis: I will like to know how to interpret this output | 15:05 |
smcginnis | armstrong: You would want the namespace too, so the line in the file should be "openstack/XX", for each relevant repo to be released. | 15:05 |
smcginnis | armstrong: Not sure what you mean. Like we went through yesterday? | 15:06 |
armstrong | https://www.irccloud.com/pastebin/QccpffyG/ | 15:07 |
armstrong | smcginnis: it says changes between 1.0.0.0rc1 and 92f8bdc and nothing else | 15:08 |
armstrong | smcginnis: but some have more info, for example: | 15:09 |
armstrong | https://www.irccloud.com/pastebin/K0iTtMOl/ | 15:09 |
smcginnis | Well, we went through all of that yesterday. Let's try something different. | 15:10 |
smcginnis | Since this output is per-repo, but we release per-"deliverable" that may contain more than one repo, you can just run the command: | 15:10 |
smcginnis | tox -e venv --notest; ./tools/process_auto_releases.sh victoria $(.tox/venv/bin/list-deliverables --series victoria --cycle-based-no-trailing) | 15:12 |
smcginnis | That will go through every victoria cycle-with-rc deliverable. | 15:12 |
smcginnis | You can see if there are changes to be released from that output. | 15:13 |
smcginnis | Most will not have anything to release, like the adjutant-ui example. | 15:13 |
smcginnis | Those you can just answer N when promted whether to do a release. | 15:13 |
smcginnis | But the ones that have changes that are not just CI related or local configuration like we identified yesterday, answer Y when prompted and then select the option for an RC when prompted. | 15:14 |
smcginnis | I'd have to look back, but I think there were only 5 or so (at least less than 10) that we say that had changes merged. | 15:14 |
smcginnis | So most of the time you will be just waiting for the output, then pressing N and enter. | 15:15 |
smcginnis | But it at least will let you review each deliverable. | 15:15 |
smcginnis | Does that make sense? | 15:15 |
armstrong | i just ran the script and it output: "Enter review topic to use: " | 15:16 |
armstrong | smcginnis: Are we running the right script? | 15:16 |
smcginnis | Yes, that looks right. | 15:17 |
smcginnis | So just pick a topic to use. Maybe victoria-final-rc? | 15:17 |
armstrong | smcginnis: ok | 15:17 |
smcginnis | armstrong: Then the commit message can be something like what was used in https://review.opendev.org/#/c/726145/ | 15:19 |
armstrong | smcginnis: ok | 15:20 |
smcginnis | But as it states, use "PROJECT" as a placeholder in the message that will be updated with the actual name. | 15:20 |
smcginnis | And break that long line into two shorter ones. ;) | 15:20 |
smcginnis | armstrong: How's it looking so far? | 15:22 |
armstrong | smcginnis: "This creates a final release candidate for the Victoria release" | 15:23 |
*** ykarel|away has quit IRC | 15:24 | |
smcginnis | armstrong: Is that what you are using for the description in the commit message? | 15:24 |
armstrong | smcginnis: I want to follow the format on the link that you suggested. | 15:26 |
smcginnis | Right. | 15:26 |
armstrong | smcginnis: but where should the "PROJECT" fit in the commit msg? | 15:26 |
smcginnis | The first summary line of the commit message. | 15:26 |
smcginnis | So to match what was done last cycle: Final RC patch for PROJECT | 15:27 |
smcginnis | Then a blank line. | 15:27 |
smcginnis | Then maybe something like: | 15:27 |
smcginnis | This creates a new RC before the final release candidate deadline to | 15:27 |
smcginnis | release the latest fixes and/or translations. | 15:27 |
smcginnis | Please ack with a +1, or if there is some reason to hold off, leave a -1. | 15:27 |
smcginnis | armstrong: Where are you at now? | 15:30 |
armstrong | smcginnis: for the commit message we are creating the final RC or new RC...? I think this is the final RC | 15:30 |
smcginnis | It's a new final RC. :) | 15:30 |
smcginnis | armstrong: What point are you at now? | 15:32 |
armstrong | smcginnis: it asked to create a stable branch and then [y/N] to continue | 15:35 |
smcginnis | armstrong: Good. And we're not creating a stable branch right now, so you just hit enter. | 15:35 |
armstrong | smcginnis: meaning I should choose [N] and not [y] | 15:36 |
smcginnis | Correct | 15:36 |
armstrong | smcginnis: I asked the action on the second step | 15:39 |
smcginnis | ? | 15:40 |
armstrong | continue with the processing? [y/N] | 15:40 |
armstrong | N is the default ? | 15:40 |
smcginnis | Yes, so if the example commit message output looks good and everything else, press "y" and enter. | 15:41 |
armstrong | let me show you the msg | 15:41 |
armstrong | https://www.irccloud.com/pastebin/wy90blbC/ | 15:41 |
smcginnis | Looks fine to me. | 15:42 |
armstrong | ok | 15:42 |
armstrong | smcginnis: this is the first project | 15:43 |
armstrong | https://www.irccloud.com/pastebin/9JTg2WgV/ | 15:43 |
smcginnis | OK, we talked about what things need a release or not. Can you go through these? Do you understand what we are looking for? | 15:43 |
armstrong | From what I understand, we are looking for projects. that jave not yet made any release yet | 15:46 |
smcginnis | Not exactly. | 15:46 |
smcginnis | Like the process guide says, we are looking for projects that have merged significant changes since their last RC release. | 15:46 |
smcginnis | We want to try to help make sure they get those final bugfixes and translations included in the RC so that the final coordinated release includes them. | 15:47 |
armstrong | smcginnis: ok | 15:47 |
armstrong | smcginnis: from the output of the first command, we see these projects of interest with commit activities for example kayobe? | 15:50 |
armstrong | https://www.irccloud.com/pastebin/Ucax7HU9/ | 15:50 |
smcginnis | Yep. But kayobe is a cycle-trailing deliverable, so that one we skip. | 15:51 |
armstrong | smcginnis: are we interested only with c-w-i and c-w-rc? | 15:53 |
smcginnis | Only the cycle-with-rc deliverables. | 15:54 |
smcginnis | Sorry, we're almost at the meeting start time, so I'd like to get these through quickly. | 15:55 |
armstrong | smcginnis: ok | 15:55 |
smcginnis | If you don't mind, I'll quick do that, then we can catch up on any questions after the meeting. | 15:55 |
armstrong | smcginnis: sure | 15:55 |
openstackgerrit | Sean McGinnis proposed openstack/releases master: Final RC patch for cloudkitty https://review.opendev.org/756875 | 15:55 |
openstackgerrit | Sean McGinnis proposed openstack/releases master: Final RC patch for heat-dashboard https://review.opendev.org/756876 | 15:55 |
*** e0ne has quit IRC | 15:55 | |
openstackgerrit | Sean McGinnis proposed openstack/releases master: Final RC patch for neutron https://review.opendev.org/756877 | 15:56 |
openstackgerrit | Sean McGinnis proposed openstack/releases master: Final RC patch for senlin-dashboard https://review.opendev.org/756878 | 15:57 |
openstackgerrit | Sean McGinnis proposed openstack/releases master: Final RC patch for tacker https://review.opendev.org/756879 | 15:57 |
openstackgerrit | Sean McGinnis proposed openstack/releases master: Final RC patch for trove https://review.opendev.org/756880 | 15:57 |
smcginnis | armstrong: The relevant deliverables (at least that I saw) are under https://review.opendev.org/#/q/topic:victoria-final-rc+(status:open+OR+status:merged) | 15:58 |
smcginnis | Those all had either translations merged or bugfixes. | 15:58 |
armstrong | smcginnis: ok | 15:58 |
smcginnis | #startmeeting releaseteam | 16:00 |
openstack | Meeting started Thu Oct 8 16:00:04 2020 UTC and is due to finish in 60 minutes. The chair is smcginnis. Information about MeetBot at http://wiki.debian.org/MeetBot. | 16:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:00 |
*** openstack changes topic to " (Meeting topic: releaseteam)" | 16:00 | |
openstack | The meeting name has been set to 'releaseteam' | 16:00 |
smcginnis | Ping list: ttx armstrong sboyron damani | 16:00 |
smcginnis | #link https://etherpad.opendev.org/p/victoria-relmgt-tracking Agenda | 16:00 |
armstrong | o/ | 16:00 |
smcginnis | We're way down on line 460 now. | 16:00 |
hberaud | o/ | 16:01 |
smcginnis | Will just wait a couple minutes for folks. | 16:01 |
sboyron | o/ | 16:01 |
* hberaud will surely eject soon | 16:01 | |
*** rpittau is now known as rpittau|afk | 16:01 | |
fungi | remember to rewind before you eject | 16:01 |
smcginnis | :) | 16:02 |
hberaud | lol | 16:02 |
smcginnis | #topic Review tasks completion | 16:02 |
*** openstack changes topic to "Review tasks completion (Meeting topic: releaseteam)" | 16:02 | |
smcginnis | Process remaining stable branch exceptions | 16:02 |
smcginnis | Looks like we got all of those through. | 16:02 |
ttx | ohai | 16:02 |
smcginnis | Notify the documentation team - I think you got that covered hberaud? | 16:03 |
hberaud | done | 16:03 |
smcginnis | We skipped testing the release process. | 16:03 |
hberaud | [doc] AJAeger submitted a related patch | 16:04 |
smcginnis | And hberaud picked up a couple tasks to update our process based on changes to things like that. | 16:04 |
smcginnis | Great! | 16:04 |
smcginnis | armstrong and I just went through the list_rc_updates task. There were only a few repos that have merged things, so just a few patches out there. | 16:04 |
smcginnis | #link https://review.opendev.org/#/q/topic:victoria-final-rc+(status:open+OR+status:merged) | 16:05 |
smcginnis | Deadline is today, so let's just give those a little time to respond. | 16:05 |
smcginnis | Should we just push those through if no response? I think in the past we actually left it up to the teams to +1. | 16:06 |
smcginnis | ttx: Thoughts? ^ | 16:07 |
hberaud | allow them to +1 | 16:07 |
ttx | allow them to +1 | 16:07 |
smcginnis | OK. And just abandon if no response? | 16:07 |
ttx | We have a fallback | 16:07 |
smcginnis | I think that's in line with how we've handled it in the past. | 16:08 |
ttx | we should only force when we have no solution | 16:08 |
hberaud | +1 | 16:08 |
smcginnis | Some good fixes might not be in the coordinated release, but at least it will be easy to pick those up in stable releases soon. | 16:08 |
smcginnis | Next task - countdown email. | 16:08 |
smcginnis | That and running the propose-final-release script will be done tomorrow. | 16:09 |
smcginnis | #topic Review countdown email | 16:09 |
*** openstack changes topic to "Review countdown email (Meeting topic: releaseteam)" | 16:09 | |
smcginnis | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 16:09 |
smcginnis | Looks like I got all the dates updated. | 16:10 |
hberaud | LGTM | 16:10 |
smcginnis | Great | 16:10 |
smcginnis | #topic Assign release week tasks | 16:10 |
*** openstack changes topic to "Assign release week tasks (Meeting topic: releaseteam)" | 16:10 | |
armstrong | LGTM! | 16:10 |
smcginnis | Hopefully it will be a quiet week. Nothing much should be happening until Wednesday. | 16:11 |
*** diablo_rojo has joined #openstack-release | 16:11 | |
* diablo_rojo joins late | 16:11 | |
smcginnis | ttx: Did you want to kick things off early in the day again? Maybe with hberaud? | 16:11 |
* smcginnis marks diablo_rojo tardy | 16:11 | |
fungi | i'll be around to help with any infra-related issues, though also doing (virtual) ansiblefest booth duty starting around 12:00 utc tuesday and wednesday | 16:11 |
hberaud | awesome | 16:12 |
smcginnis | Fun! :) | 16:12 |
ttx | yes | 16:12 |
ttx | Official announce shall be shortly before 10am CT | 16:12 |
fungi | (a.k.a. 15:00 utc) | 16:12 |
smcginnis | hberaud has signed up for teh missing-releases check. | 16:13 |
smcginnis | That checks to make sure tarballs are there and everything looks good before we (potentially) have a flood of people trying to pull them all down. | 16:13 |
smcginnis | hberaud: The update is pretty straight forward, but just ask if anything there isn't clear. | 16:14 |
hberaud | sure | 16:14 |
smcginnis | Then I will send out the release announcement email right around 1500 UTC to coordinate with the foundation press release. | 16:14 |
smcginnis | And follow that up with the announcement to openstack-discuss. | 16:15 |
sboyron | I'd like to join you hberaud on this point if you're ok | 16:15 |
hberaud | sboyron: you're welcome | 16:15 |
fungi | i can also approve the openstack-announce moderation queue, just ping me | 16:15 |
smcginnis | Great! | 16:15 |
smcginnis | fungi: Oh right, I think I will need that. | 16:15 |
smcginnis | I will ping you once it's sent. | 16:15 |
ttx | I think I can do that too | 16:16 |
smcginnis | #topic Open Floor | 16:16 |
*** openstack changes topic to "Open Floor (Meeting topic: releaseteam)" | 16:16 | |
ttx | if I can remember my password | 16:16 |
fungi | yeah, either one of us, whoever's available | 16:16 |
smcginnis | And that should be it for next weeks tasks. | 16:16 |
ttx | woohoo, another release! | 16:16 |
fungi | #link http://pool.sks-keyservers.net:11371/pks/lookup?op=vindex&search=0x5d2d1e4fb8d38e6af76c50d53d4fec30cf5ce3da&fingerprint=on Wallaby Cycle Artifact Signing Key | 16:16 |
smcginnis | And that will be it for Victoria. | 16:16 |
fungi | i finally pushed that up a couple days ago | 16:16 |
fungi | will propose the change to switch to it after next week | 16:17 |
smcginnis | Hmm: No results found: No keys found | 16:17 |
fungi | oh, it may not be replicated to all of the pool yet | 16:17 |
smcginnis | Ah, ok. | 16:17 |
smcginnis | No need for a meeting next week, assuming nothing major happens with the final release. | 16:18 |
hberaud | ack | 16:18 |
sboyron | ok | 16:18 |
smcginnis | So once the final release is out and announcements are made, I will then pass the baton to hberaud. :) | 16:18 |
fungi | #link http://sks.pod02.fleetstreetops.com:11371/pks/lookup?op=vindex&search=0x5d2d1e4fb8d38e6af76c50d53d4fec30cf5ce3da&fingerprint=on alternate keyserver url | 16:18 |
smcginnis | ++ | 16:19 |
hberaud | smcginnis: thanks :) | 16:19 |
smcginnis | Anything else to discuss today? | 16:20 |
ttx | when do we discuss PTG session content? | 16:20 |
hberaud | nothing on my end | 16:20 |
fungi | don't forget to vote if you got a ballot for teh tc or telemetry ptl elections! | 16:20 |
smcginnis | Great reminder | 16:20 |
ttx | maybe start an etherpad? | 16:20 |
elod | hi, I have one question regarding stable/stein Extended Maintenance transition if it is OK :) | 16:21 |
hberaud | ttx: do we have an exiting template? | 16:21 |
hberaud | *existing | 16:21 |
smcginnis | There are etherpads from the past PTGs. | 16:21 |
smcginnis | Not sure if that is captured anywhere once the ptg bot clears out the list though. | 16:22 |
smcginnis | Probably buried in IRC logs somewhere. | 16:22 |
hberaud | ack, I'll do a speleo session | 16:22 |
ttx | I usually started from the postmortem notes that we add at the bottom of the current tracking etherpad | 16:22 |
sboyron | hberaud: sounds like it's time for you to code tool to search on irc logs like your wonderfull mail search script ;) | 16:23 |
ttx | Like, anything weird we need to change/discuss, I add there | 16:23 |
hberaud | ttx: it's a good starting point | 16:23 |
ttx | and then add anything you think we should change/do | 16:24 |
hberaud | elod: the floor is yours | 16:25 |
elod | thanks, | 16:25 |
elod | so the deadline is in ~1 months | 16:25 |
elod | 2020-11-11 according to releases.o.o | 16:25 |
elod | usually I prepare a mail some weeks prior the deadline | 16:26 |
armstrong | Hybrid: if you don't mind, I will like to partner with you on your task for this/next week to learn how it's done. | 16:26 |
elod | i can prepare it for stein, too, if it's OK | 16:26 |
elod | and the question is when should I do that? | 16:26 |
elod | Maybe around Oct 19? | 16:27 |
hberaud | no idea | 16:27 |
smcginnis | I would say whenever you are ready. | 16:27 |
smcginnis | Doesn't hurt to have a little extra notice on that. | 16:27 |
hberaud | +1 | 16:28 |
elod | OK, then I'll do that next week | 16:28 |
armstrong | typo sorry about that | 16:28 |
smcginnis | Might be interesting to see what unreleased commits are on stable/stein. We could propose (unofficially of course) some stable releases so there isn't a rush at the end to merge things before the deadline. | 16:28 |
elod | a bit sooner, hopefully it does not interfere with the release :) | 16:28 |
armstrong | hberaud: if you don't mind, I will like to partner with you on your task for this/next week to learn how it's done. | 16:28 |
fungi | the 19th is the first day of the open infrastructure summit and forum, so that's maybe a good opportunity to talk about em impact | 16:28 |
hberaud | armstrong: sure you are welcome too | 16:29 |
elod | smcginnis: yes, just wanted to ask whether we should do some stable release patch by ourselves :) | 16:29 |
*** ricolin_ has quit IRC | 16:29 | |
hberaud | agreed with fungi | 16:30 |
smcginnis | elod: I think it helped last time I ran it. And it's pretty easy now that it's mostly automated. | 16:30 |
* ttx needs to run | 16:30 | |
elod | smcginnis: yes, that helped a lot that you did that on july | 16:30 |
* hberaud eject as well, thanks | 16:31 | |
elod | smcginnis: if the tool is in the repo then I can try to run that too | 16:31 |
elod | sorry for hijacking the end of the meeting o:) | 16:31 |
smcginnis | No, this is good. | 16:31 |
hberaud | np :) | 16:32 |
smcginnis | I think we can run: ./tools/process_auto_releases.sh victoria $(list-deliverables --series stein) | 16:32 |
elod | fungi: yes, I thought oct 19 is good because it's after the Victoria release and just the beginning of the summit :) | 16:32 |
elod | smcginnis: good, then I'll try to combine the mail and the auto-release ;) | 16:33 |
smcginnis | Sounds good! | 16:33 |
elod | \o/ | 16:33 |
*** vishalmanchanda has quit IRC | 16:34 | |
elod | thanks | 16:34 |
smcginnis | OK, anything else from anyone? | 16:35 |
sboyron | not on my side | 16:35 |
smcginnis | OK, thanks everyone. Almost there! | 16:36 |
smcginnis | #endmeeting | 16:36 |
*** openstack changes topic to "OpenStack Release Managers office - Come here to discuss how to release OpenStack components - Logged at http://eavesdrop.openstack.org/irclogs/%23openstack-release/" | 16:36 | |
openstack | Meeting ended Thu Oct 8 16:36:33 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:36 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-08-16.00.html | 16:36 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-08-16.00.txt | 16:36 |
openstack | Log: http://eavesdrop.openstack.org/meetings/releaseteam/2020/releaseteam.2020-10-08-16.00.log.html | 16:36 |
sboyron | smcginnis thanks | 16:36 |
elod | thanks smcginnis o/ | 16:36 |
diablo_rojo | thanks smcginnis! | 16:38 |
armstrong | thanks smcginnis | 16:40 |
armstrong | smcginnis: do you have time to explain something in the process, we were working on? | 16:45 |
*** dtantsur is now known as dtantsur|afk | 16:46 | |
smcginnis | armstrong: Sure! | 16:47 |
armstrong | First, how can one figure out the release-cycle that a project follows based on the output of the first command I ran? | 16:48 |
openstackgerrit | Sean McGinnis proposed openstack/releases master: Add recent release note links https://review.opendev.org/756889 | 16:49 |
smcginnis | armstrong: That script gets all deliverables for this release-cycle. | 16:49 |
armstrong | smcginnis: Sorry release model: because the release model is not available | 16:50 |
smcginnis | armstrong: For the trailing ones that were picked up, that's more understanding what is a packaging-type project. Those can be verified by looking at their deliverables files under deliverables/victoria. | 16:50 |
smcginnis | In the deliverable file, it will have type: trailing | 16:50 |
smcginnis | We used to have a release model called cycle-trailing, but that was changed recently. | 16:50 |
smcginnis | It looks like our tools need to be updated to accomodate that. | 16:51 |
smcginnis | Normally, you would not need to worry about it. For now, we need to just watch for those. | 16:51 |
armstrong | smcginnis: ok, so we have to cross-reference with another file to know the model that a project follows? | 16:51 |
smcginnis | armstrong: Basically. To be precise, it does list all deliverables that follow the cycle-with-rc model. The gotcha is that now cycle-with-rc has two types: the standard one and the trailing one. | 16:52 |
smcginnis | So once we update the tooling to handle that right, it should make it a lot easier. | 16:52 |
armstrong | ok | 16:52 |
armstrong | smcginnis: secondly, what happens to projects that are not included here: https://review.opendev.org/#/q/topic:victoria-final-rc+(status:open+OR+status:merged) ? | 16:56 |
armstrong | smcginnis: are they in good standing? | 16:56 |
smcginnis | armstrong: Nothing. The ones that are not included there are the ones that did not have changes committed that would be good to be released. | 16:56 |
armstrong | smcginnis: even if they didn't make any change during the cycle? | 16:57 |
smcginnis | armstrong: All cycle-with-rc deliverables have at least an RC1 release by this point. | 16:58 |
smcginnis | armstrong: So the task was to look for any deliverables that have merged useful changes since RC1 to encourage them to do an RC2 (or RC3) before the deadline. | 16:59 |
armstrong | smcginnis: ok I got it now | 17:00 |
smcginnis | ;) | 17:00 |
openstackgerrit | Terry Wilson proposed openstack/releases master: Release ovsdbapp 1.5.1 https://review.opendev.org/756918 | 19:00 |
*** jtomasek_ has quit IRC | 19:03 | |
openstackgerrit | Merged openstack/releases master: Add recent release note links https://review.opendev.org/756889 | 19:13 |
*** priteau has quit IRC | 19:31 | |
*** iurygregory has quit IRC | 20:00 | |
openstackgerrit | Merged openstack/releases master: Final RC patch for cloudkitty https://review.opendev.org/756875 | 20:01 |
*** iurygregory has joined #openstack-release | 20:02 | |
*** slaweq has quit IRC | 20:26 | |
*** sboyron has quit IRC | 21:05 | |
*** diablo_rojo has quit IRC | 22:11 | |
*** tosky has quit IRC | 22:59 | |
*** pmannidi has joined #openstack-release | 23:23 | |
openstackgerrit | Merged openstack/releases master: Final RC patch for trove https://review.opendev.org/756880 | 23:37 |
*** armax has quit IRC | 23:59 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!