*** tkajinam is now known as Guest213 | 08:56 | |
damani | hi | 10:09 |
---|---|---|
opendevreview | Merged openstack/etcd3gw master: Apply timeout in each request call https://review.opendev.org/c/openstack/etcd3gw/+/908585 | 10:36 |
opendevreview | Merged openstack/etcd3gw master: Update README https://review.opendev.org/c/openstack/etcd3gw/+/908582 | 10:36 |
opendevreview | Takashi Kajinami proposed openstack/oslo.utils master: add <range-in> spec DSL operator https://review.opendev.org/c/openstack/oslo.utils/+/908289 | 10:38 |
tkajinam | ^^^ damani hberaud I've updated this one based on the response from the original author. we can probably merge this before release if another core would accept it | 10:41 |
opendevreview | Merged openstack/whereto master: Install requirements for doc build https://review.opendev.org/c/openstack/whereto/+/909342 | 10:41 |
opendevreview | Adam Rozman proposed openstack/oslo.utils master: add <range-in> spec DSL operator https://review.opendev.org/c/openstack/oslo.utils/+/908289 | 11:15 |
opendevreview | Adam Rozman proposed openstack/oslo.utils master: add <range-in> spec DSL operator https://review.opendev.org/c/openstack/oslo.utils/+/908289 | 11:20 |
opendevreview | Adam Rozman proposed openstack/oslo.utils master: add <range-in> spec DSL operator https://review.opendev.org/c/openstack/oslo.utils/+/908289 | 11:22 |
opendevreview | Adam Rozman proposed openstack/oslo.utils master: add <range-in> spec DSL operator https://review.opendev.org/c/openstack/oslo.utils/+/908289 | 11:23 |
damani | tkajinam, but it's a new feature | 11:48 |
opendevreview | Merged openstack/oslo.cache master: Fix incomplete exception message https://review.opendev.org/c/openstack/oslo.cache/+/909309 | 11:55 |
damani | tkajinam, hberaud, but we can always do a request exception if you think it's necessary | 12:36 |
gthiemonge | Hi Folks, IDK if it has already been reported, but there's some spam in taskflow's launchpad: https://bugs.launchpad.net/taskflow/+bug/2054305 https://answers.launchpad.net/taskflow/+question/708887 | 12:53 |
tkajinam | damani, we can follow official FFE procedure but I think it's overkill for that specific change with limited impact and appropriate test coverage | 13:03 |
tkajinam | that's my opinion | 13:03 |
tkajinam | gthiemonge, thanks. let me report it as a smap | 13:03 |
damani | tkajinam, ok | 13:40 |
damani | hberaud, what do you think? | 13:40 |
tkajinam | I think he is also positive about merging it according to his comment in the review | 13:41 |
tkajinam | gthiemonge, I've reported that span and the report has been removed and the account has been banned. thanks for raising it. | 13:41 |
gthiemonge | tkajinam: thank you | 13:42 |
hberaud | damani, tkajinam: yeah I think we can merge it | 14:11 |
hberaud | tkajinam: Do you want replacing me in my oslo release liaison role? I'm not the most active oslo member this cycle. I think that you and damani could make a good duo. | 14:16 |
damani | hberaud, ok | 14:16 |
damani | tkajinam, hberaud, done | 14:18 |
damani | i will do all the releases little bit later or tomorrow | 14:18 |
hberaud | damani: I don't think you need to release things (apart "independent" oslo deliverables), the release team already proposed new versions for us. However, do not forget check the proposed versions, and to update the proposed SHA. At least the oslo.utils patch would require a SHA update once https://review.opendev.org/c/openstack/oslo.utils/+/908289 will merged. See => | 14:29 |
hberaud | https://review.opendev.org/q/topic:%22caracal-final-non-client-libs%22+reviewer:dbengt@redhat.com | 14:29 |
tkajinam | ah that's nice | 14:51 |
tkajinam | I was wondering if we can generate release patches by any tools but that was already done. nice | 14:51 |
hberaud | We reached the lib freeze so those patches are automatically generated by the release team as convenience patches | 14:55 |
hberaud | tkajinam: let me know if you are ok with my proposal above (release liaison), and then, if you are ok, I'll submit a patch to allow you to endorse that role. | 14:56 |
tkajinam | sounds good to me | 14:57 |
hberaud | awesome, thank you | 14:58 |
hberaud | tkajinam, damani: FYI https://review.opendev.org/c/openstack/governance/+/909455 | 15:06 |
hberaud | I removed myself from the list of the release liaison to better reflect who are really the active people and allow other developers to contact you directly rather than me | 15:09 |
hberaud | I'm still there if you need help or info | 15:10 |
hberaud | concerning the release of the stable branches, I maintained an automatically generated report https://github.com/4383/openstack.reports . A new report was generated each 2 today. A report is a commit, example https://github.com/4383/openstack.reports/commit/39eb7d95cda1056e730cccf329eb4646750ab8fc (rendering better with git log) | 15:19 |
hberaud | this report was generated by using a crontab on my laptop. My local instance seems broken, but you can fork this repo and run it on your own | 15:21 |
tkajinam | ahh that's nice | 15:22 |
hberaud | you have to update this script at the begining of each new series https://github.com/4383/openstack.reports/blob/master/tools/release_oslo.sh | 15:23 |
hberaud | to move the master to the new stable branch | 15:23 |
hberaud | this script is poorly designed and many improvements could be made (loop etc...) | 15:24 |
tkajinam | if it works then it's all fine | 15:25 |
hberaud | but even if it is not perfect it helped me during couple of years | 15:25 |
tkajinam | it's apparently better than what I do for puppet repos | 15:25 |
tkajinam | (I generate release patch manually quite often | 15:25 |
tkajinam | yeah | 15:25 |
hberaud | also you have to remove obsolete branches (eoled) from this script time to time | 15:26 |
hberaud | (obsolete from a release team point of view https://releases.openstack.org/) | 15:27 |
hberaud | the crontab will run that script, this script will commit a new report and then push it to the remote repo/fork (origin) | 15:29 |
hberaud | the crontab command is given here https://github.com/4383/openstack.reports/blob/master/tools/release_oslo.sh#L4 | 15:29 |
tkajinam | yeah makes totally sense | 15:29 |
tkajinam | probably we can drop wallaby and yoga because these are already unmaintained status. | 15:30 |
hberaud | yes | 15:30 |
hberaud | a good improvement would be to pull this kind of config directly from the official release status https://opendev.org/openstack/releases/src/branch/master/data/series_status.yaml | 15:31 |
hberaud | with a wget/curl | 15:31 |
hberaud | and then loop over the results | 15:32 |
hberaud | it would avoid updating this script each 6 months | 15:32 |
hberaud | (config = branches who are actives or not actives) | 15:33 |
damani | hberaud, tkajinam, i will check the repositoru | 15:34 |
damani | repository | 15:34 |
opendevreview | Merged openstack/oslo.utils master: add <range-in> spec DSL operator https://review.opendev.org/c/openstack/oslo.utils/+/908289 | 15:41 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!