| *** ysandeep|out is now known as ysandeep | 03:53 | |
| *** ysandeep is now known as ysandeep|ruck | 04:31 | |
| *** ysandeep|ruck is now known as ysandeep|lunch | 07:55 | |
| *** ysandeep|lunch is now known as ysandeep | 08:57 | |
| *** amoralej|off is now known as amoralej | 10:28 | |
| opendevreview | Merged openstack/releases master: Release sushy for Yoga-1 milestone https://review.opendev.org/c/openstack/releases/+/818430 | 11:01 |
|---|---|---|
| opendevreview | Merged openstack/releases master: [Puppet OpenStack] Create final stable/ussuri release https://review.opendev.org/c/openstack/releases/+/819068 | 11:05 |
| *** ysandeep is now known as ysandeep|ruck | 11:08 | |
| opendevreview | Merged openstack/releases master: [horizon] Transition Ussuri to EM https://review.opendev.org/c/openstack/releases/+/817592 | 11:10 |
| opendevreview | Dmitriy Rabotyagov proposed openstack/releases master: Release config_template https://review.opendev.org/c/openstack/releases/+/819623 | 11:16 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: [Puppet OpenStack] Transition queens to EOL https://review.opendev.org/c/openstack/releases/+/818938 | 11:31 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: [Puppet OpenStack] Transition rocky to EOL https://review.opendev.org/c/openstack/releases/+/819628 | 11:45 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: [Puppet OpenStack] Transition rocky to EOL https://review.opendev.org/c/openstack/releases/+/819628 | 12:00 |
| opendevreview | Takashi Kajinami proposed openstack/releases master: [Puppet OpenStack] Transition stein to EOL https://review.opendev.org/c/openstack/releases/+/819632 | 12:00 |
| opendevreview | Merged openstack/releases master: [oslo] Transition Ussuri to EM https://review.opendev.org/c/openstack/releases/+/817610 | 12:02 |
| opendevreview | Merged openstack/releases master: Release config_template https://review.opendev.org/c/openstack/releases/+/819623 | 12:59 |
| *** amoralej is now known as amoralej|lunch | 13:09 | |
| *** tosky is now known as Guest7142 | 13:37 | |
| *** tosky_ is now known as tosky | 13:37 | |
| gthiemonge | Hi Folks, I proposed a backport for Octavia stable/wallaby that updates setup.cfg (it adds a new entry point), do you think it would be an acceptable backport? This commit is important for people who want to run Octavia Wallaby on upcomming distribs (ex Centos 9 Stream) https://review.opendev.org/c/openstack/octavia/+/807310 | 13:55 |
| *** ysandeep|ruck is now known as ysandeep|out | 13:58 | |
| *** amoralej|lunch is now known as amoralej | 14:07 | |
| elodilles | hi gthiemonge , i had a quick look at the patch. Adding a new 'entry point' to setup.cfg is not an issue, so that would not be a problem (well, feature backports are not welcome on stable branches, so if that introduces some complex changes, then the case is different). on the other hand, as far as i see the patch *replaces* some old behavior with a new one (is it some kind of an API | 14:20 |
| elodilles | change?), which is not fortunate and I'd recommend not to backport that | 14:20 |
| *** ykarel is now known as ykarel|away | 14:27 | |
| gthiemonge | elodilles: it doesn't change the API, this is purely an internal change. It doesn't provide any new stuff, except compatibility with modern distros. That was discussed during the Octavia PTG and our conclusion was that it should be backported... the only concern was this new entry point, I believe it may break packages | 14:35 |
| elodilles | gthiemonge: i did not know that a new entry point in setup.cfg could break packages. the real concern is not just breaking packages, i'd say, but also changing behavior which could cause problems for consumers of stable releases. or even regressions. | 14:48 |
| elodilles | the general rules are listed here: https://docs.openstack.org/project-team-guide/stable-branches.html#appropriate-fixes | 14:50 |
| elodilles | (and some other details under 'review guidelines': https://docs.openstack.org/project-team-guide/stable-branches.html#review-guidelines ) | 14:52 |
| gthiemonge | elodilles: I think the package needs to have the explicit list of the entrypoints to create the appropriate scripts in xxx/bin (that comes from my previous experiences with RPMs) | 14:52 |
| elodilles | gthiemonge: i see, thanks for the explanation | 15:03 |
| elodilles | gthiemonge: i'd say i am less worried about downstream packaging issues (but maybe I am wrong with this). the problem is really about would it be possible that for example some consumer of stable releases installs the package and causes them regression, something is working differently that they were relied on | 15:06 |
| elodilles | for example if someone is using octavia's wallaby on older/other distros, could they have a problem by simply upgrading to the new package? | 15:10 |
| gthiemonge | yeah I see your point. Updating should be transparent for users/admins. And this backport would help us to fix some other bugs in Octavia | 15:19 |
| *** amoralej is now known as amoralej|off | 16:29 | |
| *** marios is now known as marios|out | 16:50 | |
| opendevreview | Elod Illes proposed openstack/releases master: [Puppet OpenStack] Transition Ussuri to EM https://review.opendev.org/c/openstack/releases/+/817611 | 16:50 |
| opendevreview | Elod Illes proposed openstack/releases master: [Puppet OpenStack] Transition Ussuri to EM https://review.opendev.org/c/openstack/releases/+/817611 | 16:52 |
| opendevreview | Elod Illes proposed openstack/releases master: [Puppet OpenStack] Transition Ussuri to EM https://review.opendev.org/c/openstack/releases/+/817611 | 17:14 |
| *** ysandeep|out is now known as ysandeep | 17:25 | |
| *** ysandeep is now known as ysandeep|out | 17:58 | |
| *** tosky is now known as Guest7167 | 20:17 | |
| *** tosky_ is now known as tosky | 20:17 | |
| *** tosky_ is now known as tosky | 21:57 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!