| *** bauzas_ is now known as bauzas | 03:23 | |
| *** thuvh1 is now known as thuvh | 03:47 | |
| *** bauzas_ is now known as bauzas | 04:37 | |
| opendevreview | Hoai-Thu Vuong proposed openstack/releases master: Release monasca for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923487 | 07:57 |
|---|---|---|
| opendevreview | Elod Illes proposed openstack/releases master: Release osc-placement for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923118 | 09:59 |
| opendevreview | Hoai-Thu Vuong proposed openstack/releases master: Release monasca for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923487 | 10:28 |
| opendevreview | Merged openstack/releases master: Release python-vitrageclient for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923139 | 11:32 |
| opendevreview | Merged openstack/releases master: Release tosca-parser for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923141 | 11:32 |
| opendevreview | Merged openstack/releases master: Release keystoneauth for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923114 | 11:32 |
| opendevreview | Merged openstack/releases master: Release python-magnumclient for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923134 | 11:32 |
| opendevreview | Merged openstack/releases master: Release python-observabilityclient for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923138 | 11:36 |
| elodilles | reminder: meeting starts in less than 10 mins | 12:51 |
| elodilles | #startmeeting releaseteam | 13:01 |
| opendevmeet | Meeting started Fri Jul 5 13:01:21 2024 UTC and is due to finish in 60 minutes. The chair is elodilles. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:01 |
| opendevmeet | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:01 |
| opendevmeet | The meeting name has been set to 'releaseteam' | 13:01 |
| hberaud | o/ | 13:01 |
| elodilles | Ping list: release-team elod | 13:01 |
| elodilles | o/ | 13:01 |
| elodilles | #link https://etherpad.opendev.org/p/dalmatian-relmgt-tracking | 13:01 |
| elodilles | we are @ L205 | 13:02 |
| elodilles | OK, let's start! | 13:04 |
| elodilles | #topic Review task completion | 13:04 |
| elodilles | 1st task: 'Generate release requests for all cycle-with-intermediary libraries which had changes, but did not release since milestone-1. (elod)' | 13:04 |
| elodilles | patches were generated: https://review.opendev.org/q/topic:dalmatian-milestone-2 | 13:05 |
| elodilles | and almost all have been merged | 13:05 |
| elodilles | thanks for the reviews o/ | 13:05 |
| elodilles | there are only 2 that remained | 13:05 |
| elodilles | i was hesitant with the osc-placement's version bump | 13:06 |
| elodilles | python_requires is still set as >=3.8, but the python 3.8 classifier is dropped | 13:06 |
| hberaud | good point | 13:07 |
| elodilles | so it's somewhat dropping py38, but not completely | 13:07 |
| hberaud | I think it is good to propose a major version like you did | 13:08 |
| elodilles | i don't know which is stronger for pypi. so good question if, like this, pypi would still offer the package to py38 environments the package for download, or not | 13:08 |
| hberaud | no idea | 13:08 |
| elodilles | ++ | 13:08 |
| elodilles | anyway, i'll ping the team for a quick double-check | 13:09 |
| elodilles | the second one is about monasca, which was an inactive project up till now | 13:10 |
| elodilles | #link https://review.opendev.org/c/openstack/releases/+/923487 | 13:10 |
| elodilles | i'm not sure whether monasca is in the state where we could include in 2024.2 Dalmatian | 13:10 |
| elodilles | and we are just in the week of 2024.2 Dalmatian content freeze :S | 13:11 |
| elodilles | anyway, let's move on, we could discuss this after the meeting, or next week, when ttx and frickler are also around | 13:12 |
| elodilles | 2nd task: 'Catch if there are acl issues in newly created repositories. (elod)' | 13:12 |
| elodilles | empty output from the script, so we should be good with this | 13:12 |
| elodilles | and that was all about tasks | 13:12 |
| elodilles | so let's move on to the next topic | 13:13 |
| elodilles | #topic Assign R-12 and R-10 week tasks | 13:13 |
| elodilles | i've added my name to the tasks | 13:13 |
| elodilles | but if anyone is interested in any of the tasks, then feel free to highjack :) | 13:14 |
| hberaud | thanks | 13:14 |
| elodilles | np :) | 13:14 |
| elodilles | #topic Review countdown email for week R-12 | 13:14 |
| elodilles | #link https://etherpad.opendev.org/p/relmgmt-weekly-emails | 13:15 |
| elodilles | please take a look ^^^ | 13:15 |
| hberaud | lgtm | 13:16 |
| elodilles | thanks o/ will send it later today | 13:16 |
| hberaud | time flies | 13:16 |
| elodilles | :) | 13:16 |
| elodilles | yepp, we passed Dalmatian-2 :-o | 13:17 |
| elodilles | #topic Open Discussion | 13:17 |
| elodilles | anything to mention? | 13:17 |
| hberaud | nope | 13:19 |
| elodilles | neither from me | 13:19 |
| elodilles | then let's close the meeting! | 13:20 |
| elodilles | thanks for participating hberaud o/ | 13:20 |
| elodilles | #endmeeting | 13:20 |
| opendevmeet | Meeting ended Fri Jul 5 13:20:32 2024 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 13:20 |
| opendevmeet | Minutes: https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-07-05-13.01.html | 13:20 |
| opendevmeet | Minutes (text): https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-07-05-13.01.txt | 13:20 |
| opendevmeet | Log: https://meetings.opendev.org/meetings/releaseteam/2024/releaseteam.2024-07-05-13.01.log.html | 13:20 |
| hberaud | np :) | 13:20 |
| hberaud | thanks elodilles | 13:20 |
| elodilles | np :] | 13:20 |
| fungi | hberaud: elodilles: trove classifiers are purely advisory, no installers i'm aware of take them into consideration (especially not pip). the python_requires is really the only thing installers look at to determine whether something can be installed for the current interpreter version | 13:34 |
| hberaud | taking note of that | 13:34 |
| hberaud | thanks | 13:35 |
| fungi | so if you want to soft-deprecate a python interpreter version, removing the trove classifier saying you support it while not increasing requires_python right away has the desired effect of not immediately breaking consumers of a new release of the package on the older python interpreter | 13:35 |
| hberaud | and classifiers are not used at all? | 13:36 |
| fungi | it's a way of saying "we're no longer testing that things work with this version of python, but you're welcome to try it anyway" | 13:36 |
| hberaud | how pip determines the max version? | 13:36 |
| fungi | trove classifiers are used for communicating things to users, mainly in the warehouse (pypi) ui | 13:37 |
| elodilles | fungi: cool, thanks for the details! in that case here we should not bump MAJOR version. I'm updating the patch accordingly then. | 13:37 |
| hberaud | I mean imagine I've a classifier for py3.11 a python_requires with py3.9, but I'm on a py3.12 env, is it ok for pip? | 13:37 |
| opendevreview | Elod Illes proposed openstack/releases master: Release osc-placement for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923118 | 13:38 |
| hberaud | I guess that yes, pip will implicitly pull the latest version of the module | 13:39 |
| fungi | hberaud: as in if a project wants to declare that it doesn't work with some newer version of python? there's currently no good way in the packaging ecosystem to do that, and it's not clear that it would be a good idea even if there were. package metadata is tied to the release, so if you were to be able to say "this release won't work with python newer than 3.12" without knowing | 13:39 |
| fungi | whether or not that's actually true, people won't be able to install it on 3.13 until you make a new release that updates that restriction (which might be never if you're not a particularly active maintainer) | 13:39 |
| hberaud | I see | 13:40 |
| hberaud | indeed | 13:40 |
| fungi | also pip starts with the newest version of the package and works its way back until it finds one whose requirements can be met, so since you can't go back in time and alter metadata for prior releases it will just happily rewind to an old enough package version where you didn't realize you wanted to set that restriction | 13:40 |
| hberaud | ack | 13:41 |
| fungi | you can actually set < conditions in python_requires expressions, but there's some consensus in the packaging community that it's a terrible idea, and also it results in some unpredictable behaviors | 13:42 |
| hberaud | yeah I can imagine the problem | 13:49 |
| frickler | sorry, I was somehow thinking the meeting would be skipped this week | 13:53 |
| frickler | and I sure am very skeptical about monasca | 13:53 |
| *** bauzas_ is now known as bauzas | 14:30 | |
| *** bauzas_ is now known as bauzas | 15:17 | |
| *** bauzas_ is now known as bauzas | 15:38 | |
| *** pdeore_ is now known as pdeore | 16:12 | |
| pdeore | elodilles, hberaud, glance is waiting for one patch to get merged, related to cve but it's stuck in gate atm, can we tag m2 on monday ? | 16:16 |
| gmann | elodilles: just wondering, what is plan for the watcher release for m-2 (is it up for review)? dan fixed its gate and it is green now and volunteer to +1 on release thing (release liaison) https://review.opendev.org/c/openstack/governance/+/923583 | 16:34 |
| gmann | background: this project was leaderless but not marked as inactive as we see some interest in this project. but plan is to move it to DPL model ^^ and do release for this cycle. | 16:35 |
| gmann | "elodilles: just wondering, what is plan for the watcher release for m-2 (is it up for review)? dan fixed its gate and it is green now and volunteer to +1 on release thing (release liaison) https://review.opendev.org/c/openstack/governance/+/923583 | 16:37 |
| gmann | background: this project was leaderless but not marked as inactive as we see some interest in this project. but plan is to move it to DPL model ^^ and do release for this cycle." | 16:37 |
| gmann | dansmith: ^^ this is what i asked to elodilles about watcher release | 16:38 |
| dansmith | thanks | 16:39 |
| pdeore | elodilles, hberaud, frickler, glance is waiting for one patch to get merged, related to cve but it's stuck in gate atm, can we tag m2 on monday ? | 16:43 |
| elodilles | pdeore: sure, no problem, to tell you the truth, milestone releases of cycle-with-rc projects are not a must, hence we do not follow them that strictly, afaik | 16:53 |
| elodilles | pdeore: feel free to propose the m2 patch for glance whenever the team is ready for it | 16:54 |
| elodilles | gmann dansmith : works for me. i see that watcher deliverables are still listed / part of 2024.2 Dalmatian release, so it's completely OK to me | 16:56 |
| pdeore | elodilles, ack Thanks !! :) | 16:56 |
| elodilles | i don't think that any of the release team would object about the transition to DPL | 16:56 |
| elodilles | pdeore: np :) | 16:56 |
| elodilles | gmann dansmith : so, thanks for the heads up :) | 16:57 |
| gmann | elodilles: thanks, so as it is with cycle-with-rc model, release can be done anytime befoer final release deadline and m-2 release is not must right? | 16:58 |
| gmann | I missed to check the cycle-with-rc model for wacther | 16:58 |
| elodilles | gmann: exactly | 16:59 |
| dansmith | sweet :) | 16:59 |
| gmann | elodilles: thanks for pointing that and confirmation | 16:59 |
| elodilles | gmann: python-watcherclient is cycle-with-intermediary but there were no functional changes i think, hence there were no generated d-2 patch | 16:59 |
| gmann | elodilles: ack | 17:00 |
| elodilles | gmann: at dalmatian-3 we'll propose a release patch anyway for python-watcherclient, even if there are only non-functional changes merged | 17:01 |
| elodilles | gmann dansmith : so just for the record, there are 4 watcher deliverables: watcher, watcher-dashboard (c-w-rc); python-watcherclient, watcher-tempest-plugin (cycle-with-intermediary) | 17:02 |
| dansmith | oh, I didn't even know watcher-dashboard was a thing :P | 17:03 |
| elodilles | :] | 17:04 |
| gmann | watcher-tempest-plugin also no changes except the CI bits but we can do release during end of cycle and if gate is all green. | 17:05 |
| elodilles | yepp | 17:05 |
| *** bauzas_ is now known as bauzas | 17:39 | |
| *** bauzas_ is now known as bauzas | 20:44 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!