*** tosky has quit IRC | 00:17 | |
*** ianychoi has joined #openstack-release | 02:09 | |
*** armax has joined #openstack-release | 04:25 | |
*** armax has quit IRC | 04:26 | |
*** ykarel|away has joined #openstack-release | 04:40 | |
*** ykarel|away is now known as ykarel | 04:41 | |
ykarel | Review please puppet-nova release for train/ussuri:- https://review.opendev.org/c/openstack/releases/+/774876 | 05:00 |
---|---|---|
*** evrardjp has quit IRC | 05:33 | |
*** evrardjp has joined #openstack-release | 05:33 | |
*** whoami-rajat__ has joined #openstack-release | 06:03 | |
*** vishalmanchanda has joined #openstack-release | 06:22 | |
*** diablo_rojo has quit IRC | 06:55 | |
*** sboyron_ has joined #openstack-release | 07:10 | |
*** eolivare has joined #openstack-release | 07:39 | |
*** slaweq has joined #openstack-release | 07:44 | |
*** ykarel has quit IRC | 07:44 | |
*** ykarel has joined #openstack-release | 07:46 | |
*** rpittau|afk is now known as rpittau | 07:53 | |
openstackgerrit | Tobias Urdin proposed openstack/releases master: Release magnum-ui 5.4.0 for Train https://review.opendev.org/c/openstack/releases/+/775078 | 08:17 |
*** jbadiapa has joined #openstack-release | 08:26 | |
*** ianychoi has quit IRC | 08:33 | |
*** tosky has joined #openstack-release | 08:36 | |
*** ianychoi has joined #openstack-release | 08:48 | |
*** hberaud has quit IRC | 08:58 | |
*** hberaud has joined #openstack-release | 08:58 | |
*** ykarel is now known as ykarel|lunch | 09:33 | |
*** dtantsur|afk is now known as dtantsur | 10:00 | |
*** jbadiapa has quit IRC | 10:04 | |
*** ykarel|lunch is now known as ykarel | 10:36 | |
*** jbadiapa has joined #openstack-release | 10:49 | |
ykarel | hberaud, review please https://review.opendev.org/c/openstack/releases/+/774876 | 10:50 |
hberaud | ykarel: done | 11:00 |
ykarel | hberaud, Thanks | 11:01 |
openstackgerrit | Merged openstack/releases master: release new version of vitrage/vitrage-dashboard https://review.opendev.org/c/openstack/releases/+/774783 | 11:20 |
openstackgerrit | Merged openstack/releases master: Release oslo.metrics 0.2.1 https://review.opendev.org/c/openstack/releases/+/774751 | 11:21 |
openstackgerrit | Merged openstack/releases master: Create new release of puppet-nova for ussuri and train https://review.opendev.org/c/openstack/releases/+/774876 | 11:21 |
openstackgerrit | Dmitry Tantsur proposed openstack/releases master: Release metalsmith 1.2.1 for Victoria https://review.opendev.org/c/openstack/releases/+/775128 | 12:00 |
openstackgerrit | Dmitry Tantsur proposed openstack/releases master: Release metalsmith 1.4.1 for Wallaby https://review.opendev.org/c/openstack/releases/+/775131 | 12:01 |
openstackgerrit | Iury Gregory Melo Ferreira proposed openstack/releases master: Release bifrost bugfix/10.1.0 for wallaby https://review.opendev.org/c/openstack/releases/+/775150 | 13:08 |
*** e0ne has joined #openstack-release | 13:09 | |
*** nweinber has joined #openstack-release | 13:38 | |
*** stand has quit IRC | 13:54 | |
*** vishalmanchanda has quit IRC | 14:14 | |
*** armstrong has joined #openstack-release | 14:21 | |
*** ykarel_ has joined #openstack-release | 14:26 | |
*** ykarel has quit IRC | 14:29 | |
openstackgerrit | Daniel Bengtsson proposed openstack/releases master: New bugfix and feature releases for oslo. https://review.opendev.org/c/openstack/releases/+/775161 | 14:30 |
*** ykarel_ has quit IRC | 14:49 | |
openstackgerrit | Dmitry Tantsur proposed openstack/releases master: Release ironic for stable/train https://review.opendev.org/c/openstack/releases/+/773049 | 14:53 |
*** diablo_rojo has joined #openstack-release | 14:56 | |
openstackgerrit | Hervé Beraud proposed openstack/releases master: Move placement under the nova team https://review.opendev.org/c/openstack/releases/+/775182 | 15:05 |
openstackgerrit | Daniel Bengtsson proposed openstack/releases master: New bugfix and feature releases for oslo. https://review.opendev.org/c/openstack/releases/+/775161 | 15:07 |
*** ricolin has joined #openstack-release | 15:08 | |
*** e0ne has quit IRC | 15:11 | |
openstackgerrit | Merged openstack/releases master: Release metalsmith 1.4.1 for Wallaby https://review.opendev.org/c/openstack/releases/+/775131 | 15:33 |
-openstackstatus- NOTICE: Recent POST_FAILURE results from Zuul for builds started prior to 15:47 UTC were due to network connectivity issues reaching one of our log storage providers, and can be safely rechecked | 15:51 | |
*** ricolin has quit IRC | 15:56 | |
hberaud | FYI we experience the same issue => http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020428.html | 15:56 |
openstackgerrit | Merged openstack/releases master: Add Extra ATC during R-7 https://review.opendev.org/c/openstack/releases/+/774999 | 15:58 |
hberaud | I think we should start to hold approval | 15:58 |
hberaud | at least for a awhile. I just see => http://lists.openstack.org/pipermail/release-job-failures/2021-February/001513.html | 15:59 |
hberaud | elod, smcginnis, ttx ^ | 15:59 |
hberaud | We can't get the logs | 16:00 |
hberaud | So it's not possible to know if this is a legit error or just a side effect of http://lists.openstack.org/pipermail/openstack-discuss/2021-February/020428.html | 16:01 |
elod | hberaud: ack. btw, the openstackstatus above ^^^ might suggest it's over | 16:01 |
hberaud | elod: yes probably | 16:02 |
elod | anyway, it doesn't hurt to wait a bit :) | 16:03 |
hberaud | however the fail ^ was after the openstackstatus | 16:03 |
hberaud | I can't check the logs so I can't get precise timestamp | 16:04 |
hberaud | The mail was send at 15:53:02 UTC | 16:05 |
hberaud | and the openstackstatus at 15:51:55 UTC | 16:05 |
hberaud | But maybe the job was already running before 15:51 | 16:06 |
ttx | yes we'll likely need to reenqueue the commit ref to retrigger post jobs /cc fungi | 16:24 |
fungi | if they were caught up in the ovh dallas network problem, then they failed at the point where the build logs were being uploaded, so whatever the job itself was supposed to do it probably still did... but if there were jobs depending on that job succeeding they were likely skipped | 16:30 |
fungi | hberaud: the failure being after the time in the status announcement is expected if the build was enqueued before that time | 16:31 |
fungi | the log upload location is decided when the build is enqueued, since it's part of thebase job | 16:32 |
fungi | the base job | 16:32 |
hberaud | ack | 16:33 |
hberaud | The failure is related to the metalsmith patch (https://review.opendev.org/c/openstack/releases/+/775131) https://opendev.org/openstack/releases/commit/5dfeec7fe5764e01d3880c285cf0265fe2209328 https://zuul.opendev.org/t/openstack/builds?job_name=tag-releases | 16:42 |
hberaud | Everything seems to have been successfully created, the tag (https://opendev.org/openstack/metalsmith/src/tag/1.4.1) and the pypi upload too (https://pypi.org/project/metalsmith/1.4.1/) | 16:42 |
hberaud | However the docs job have been skipped | 16:43 |
hberaud | fungi: Can we reenqueue for the doc part? the `tag-releases` will be ignored as already exist, isn't? | 16:45 |
clarkb | hberaud: if the docs jobs run for regular merges ( I think they do for many projects) you can just land an update to the docs too | 16:49 |
clarkb | and I think the way the jobs are setup will produce the tagged docs too (but its been a long time since I looked at the inner workings there) | 16:49 |
hberaud | clarkb: I see | 16:50 |
fungi | https://zuul.opendev.org/t/openstack/buildset/484d2f5e7b03413188b0b2b478f5e4e6 | 16:50 |
fungi | that was the buildset | 16:50 |
fungi | so the skipped docs job was for openstack/releases in the release-post pipeline | 16:51 |
fungi | presumably the next time publish-tox-docs-releases runs it'll be caught up? | 16:51 |
ttx | if the release is up on PyPI we can assume everything is good | 16:51 |
ttx | yeah | 16:52 |
hberaud | I think that yes | 16:52 |
*** ricolin has joined #openstack-release | 16:56 | |
hberaud | #startmeeting releaseteam | 17:00 |
openstack | Meeting started Thu Feb 11 17:00:05 2021 UTC and is due to finish in 60 minutes. The chair is hberaud. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:00 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
*** openstack changes topic to " (Meeting topic: releaseteam)" | 17:00 | |
openstack | The meeting name has been set to 'releaseteam' | 17:00 |
hberaud | #link https://etherpad.opendev.org/p/wallaby-relmgt-tracking Agenda | 17:00 |
hberaud | Ping list: ttx armstrong elod, damani | 17:00 |
ttx | o/ | 17:00 |
armstrong | o/ | 17:00 |
elod | o/ | 17:00 |
hberaud | We're way down on line 324 now. | 17:00 |
hberaud | Will just wait a couple minutes for folks. | 17:00 |
damani | hi | 17:00 |
*** bdodd has quit IRC | 17:01 | |
hberaud | Ok let's go | 17:03 |
hberaud | #topic Review task completion | 17:03 |
*** openstack changes topic to "Review task completion (Meeting topic: releaseteam)" | 17:03 | |
hberaud | Generate a list of intermediary-released service deliverables that have not done a release in this cycle yet. => Done | 17:03 |
hberaud | Only swift met the conditions => https://review.opendev.org/c/openstack/releases/+/774682 | 17:03 |
hberaud | And vitrage-dashboard but they proposed new releases so I think we can abandon => https://review.opendev.org/c/openstack/releases/+/774683 | 17:04 |
hberaud | Thanks armstrong | 17:04 |
ttx | I'd say it's unlikely that they will change (swift) | 17:04 |
ttx | since they have always been in the release-as-needed model | 17:04 |
hberaud | No idea, I'll see that after the countdown email that will speak about | 17:05 |
hberaud | Let's wait a bit about for feedback from them | 17:05 |
hberaud | Next task | 17:05 |
hberaud | Start a ML thread about recent release failures with tripleo deliverables on ussuri => Done thanks ttx | 17:06 |
hberaud | However you said that we need to reenqueue os-collect-config 11.0.2 and tripleo-ipsec 9.3.1 (or release 11.0.3 and 9.3.2 on stable/ussuri) | 17:06 |
*** ricolin has quit IRC | 17:06 | |
hberaud | right? | 17:06 |
hberaud | Do you want to handle that point? | 17:06 |
ttx | I'll leave choice to fungi | 17:07 |
ttx | (between reenqueuing and rereleasing) | 17:07 |
hberaud | ok | 17:08 |
ttx | not sure how easy it is to get those refs | 17:08 |
hberaud | I would argue that releasing 11.0.3 and 9.3.2 is more straightforward | 17:09 |
ttx | well, we can do it, but that means 11.0.2 and 9.3.1 are nowhere to be found | 17:09 |
hberaud | Exact | 17:10 |
ttx | so it's suboptimal compared to reenqueuing | 17:10 |
hberaud | Yes | 17:10 |
hberaud | Well I added this point to the next week tasks I think we can continue for now. Let's wait a bit for fungi's feedback | 17:11 |
hberaud | We'll update the task accordingly | 17:11 |
fungi | yep, sorry, also on a conference call, catching up | 17:12 |
hberaud | np | 17:12 |
fungi | what was the failure condition? | 17:12 |
fungi | tags got pushed but pypi uploads didn't happen? | 17:13 |
hberaud | Good question, I don't really remember | 17:13 |
ttx | Tag was not pushed | 17:13 |
ttx | tag-release job failed before that | 17:13 |
ttx | That's the post job that runs on a openstack/releases merge | 17:14 |
hberaud | I wonder why I can't retrieve the point on our previous agenda | 17:14 |
fungi | #link http://lists.openstack.org/pipermail/openstack-discuss/2021-January/020112.html | 17:14 |
fungi | that's a message i had saved to look into, but have been swamped | 17:14 |
ttx | So I'd say the ref that needs reenqueing in that commit on openstack/releases | 17:14 |
ttx | which should retrigger the post jobs | 17:15 |
hberaud | IIRC It was due to a lack of stable branches | 17:15 |
ttx | yeah we did fix the stable branch situation, but of course that did not retrigger those post jobs | 17:16 |
hberaud | Yes exact | 17:16 |
hberaud | So I think that reenqueuing could work now | 17:16 |
fungi | willing to give that a shot | 17:17 |
hberaud | Thanks | 17:17 |
fungi | so reenqueue those two openstack/releases changes into the release-post pipeline? | 17:17 |
hberaud | Hm yes | 17:17 |
fungi | should be able to do that once this call ends | 17:18 |
hberaud | Worth trying | 17:18 |
hberaud | I think we can continue, anything else about this point? | 17:20 |
ttx | nope | 17:20 |
hberaud | I leave the next week task to be sure to not forget that | 17:21 |
hberaud | #topic Socialize `test-release-openstack` nodeset switch to focal | 17:21 |
*** openstack changes topic to "Socialize `test-release-openstack` nodeset switch to focal (Meeting topic: releaseteam)" | 17:21 | |
hberaud | Just a heads up about a recent change merged yesterday and related to our `test-release-openstack` | 17:22 |
hberaud | nodeset have been switched to focal | 17:22 |
ttx | what is the expected impact? | 17:22 |
fungi | a number of the release jobs themselves are already using an ubuntu-focal nodeset anyway, right? | 17:23 |
hberaud | I don't expect issue as all our jobs are already on focal, but worth to mention it during the meeting | 17:23 |
hberaud | Yes | 17:23 |
hberaud | AFAIK it was the last one on bionic | 17:23 |
hberaud | https://opendev.org/openstack/project-config/commit/3310a349a4ecf8187f242b9a8fe7d62465f3e083 | 17:23 |
fungi | yeah, it's just that opendev is behind on scheduling a default nodeset switch from ubuntu-bionic to ubuntu-focal | 17:24 |
fungi | i want to start pushing on that in the next week | 17:24 |
hberaud | np | 17:24 |
fungi | focal's already almost a year old, we should have done it sooner | 17:24 |
fungi | but setting it explicitly in jobs now is a good way to find out whether they'll break too | 17:24 |
hberaud | Yes | 17:25 |
hberaud | So if you observe strange behavior then remember that topic | 17:25 |
hberaud | I think that's all for this point | 17:26 |
hberaud | #topic Onboarding Elod | 17:27 |
*** openstack changes topic to "Onboarding Elod (Meeting topic: releaseteam)" | 17:27 | |
hberaud | elod: thing promised thing due https://giphy.com/gifs/mlb-alds-2018-3Mb5hvWOLe8hq6gZHc | 17:27 |
armstrong | Onboarding going on here? | 17:27 |
hberaud | Welcome on board elod | 17:27 |
elod | :D | 17:27 |
armstrong | oh hahaha | 17:28 |
hberaud | Now I need to figure it how to give you the ACLs :) | 17:29 |
elod | thx :) I'll work on doing useful reviews :) | 17:29 |
hberaud | ttx: any idea ^ | 17:29 |
ttx | https://review.opendev.org/admin/groups/5c75219bf2ace95cdea009c82df26ca199e04d59,members | 17:30 |
ttx | I guess we can do a bit of cleanup too | 17:30 |
hberaud | Yes | 17:30 |
hberaud | Thanks for the link | 17:30 |
ttx | removing inactive members... although I'd keep Doug around since he still does reno reviews | 17:31 |
hberaud | Elod you are now in the list let me know if that work for you => https://review.opendev.org/admin/groups/5c75219bf2ace95cdea009c82df26ca199e04d59,members | 17:31 |
ttx | ok that should work | 17:31 |
hberaud | evrardjp had officialized is departure during last cycle | 17:32 |
elod | hberaud: i have the +2, so it works \o/ | 17:32 |
hberaud | \o/ | 17:32 |
hberaud | I updated Jean Philippe | 17:33 |
hberaud | ttx: any idea about Kendall? | 17:33 |
hberaud | AFAIK she is more or less still active | 17:34 |
ttx | She has been focusing on her TC vice-chair role | 17:34 |
ttx | I'd ask her if she plans to take up core reviews again in the future, or if we can downgrade her to mere +1 | 17:35 |
hberaud | ack | 17:35 |
hberaud | Then for now I think we are ok with the cleanup | 17:36 |
hberaud | WFY? | 17:36 |
ttx | yes | 17:37 |
hberaud | Ok move on | 17:37 |
hberaud | #topic Review countdown email contents | 17:37 |
*** openstack changes topic to "Review countdown email contents (Meeting topic: releaseteam)" | 17:37 | |
hberaud | https://etherpad.opendev.org/p/relmgmt-weekly-emails | 17:37 |
hberaud | I didn't speak about vitra-dashboard as they already gave us a response about cycle-with-rc | 17:38 |
ttx | hmm, that sounds a bit aggressive | 17:38 |
ttx | " In absence of answer by the end of R-10 week we'll consider | 17:38 |
ttx | that the switch to cycle-with-rc is preferable. | 17:38 |
ttx | " | 17:38 |
ttx | I'm not sure we can make that switch without any team feedback | 17:39 |
hberaud | Ok so we need to upgrade our doc | 17:39 |
hberaud | too | 17:39 |
ttx | Let me try to make it a bit sweeter | 17:39 |
hberaud | Feel free | 17:39 |
ttx | ok taht sounds a bit less definitive | 17:43 |
hberaud | Definitelly | 17:43 |
ttx | Otherwise looks good | 17:43 |
hberaud | I'll propose a patch for your doc to reflect that | 17:43 |
ttx | maybe we could say that we'll approve the Xena release schedule by DATE? | 17:43 |
*** rpittau is now known as rpittau|afk | 17:43 | |
hberaud | Yes | 17:44 |
hberaud | Deadline is next week, exact? | 17:44 |
hberaud | "Make sure the next development series name has been added to the data/series_status.yaml file." | 17:44 |
hberaud | Looks like yes | 17:45 |
*** dtantsur is now known as dtantsur|afk | 17:45 | |
hberaud | Yeah I agree we don't need to speak about 24w | 17:45 |
ttx | ok done | 17:46 |
hberaud | Awesome, I'll send it tomorrow | 17:46 |
hberaud | #topic Assign R-8 tasks | 17:46 |
*** openstack changes topic to "Assign R-8 tasks (Meeting topic: releaseteam)" | 17:46 | |
hberaud | done | 17:47 |
hberaud | everything is already assigned | 17:47 |
hberaud | #topic Open floor | 17:47 |
*** openstack changes topic to "Open floor (Meeting topic: releaseteam)" | 17:47 | |
hberaud | Anything else to discuss today? | 17:47 |
ttx | no | 17:47 |
elod | nothing from me either | 17:48 |
armstrong | nothing | 17:48 |
hberaud | OK, thanks everyone. Almost there! | 17:49 |
ttx | Thanks hberaud ! | 17:49 |
hberaud | #endmeeting | 17:50 |
*** 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/" | 17:50 | |
openstack | Meeting ended Thu Feb 11 17:50:01 2021 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:50 |
elod | thanks o/ | 17:50 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-02-11-17.00.html | 17:50 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-02-11-17.00.txt | 17:50 |
openstack | Log: http://eavesdrop.openstack.org/meetings/releaseteam/2021/releaseteam.2021-02-11-17.00.log.html | 17:50 |
*** bdodd has joined #openstack-release | 17:54 | |
fungi | sudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/os-collect-config --ref=refs/tags/11.0.2 --newrev=4bd71a59bd1b7a36f868bb3203f81caab4d9cf81 | 17:58 |
fungi | sudo zuul enqueue-ref --tenant=openstack --trigger=gerrit --pipeline=release --project=openstack/tripleo-ipsec --ref=refs/tags/9.3.1 --newrev=9bb150229efa276472fc986399240bb0186003dd | 17:58 |
fungi | i've done those ^ just now | 17:58 |
hberaud | awesome | 18:01 |
hberaud | fungi: thanks | 18:02 |
fungi | any time | 18:02 |
hberaud | fungi: both failed | 18:17 |
fungi | i'll have to have a look after my current meeting wraps up | 18:19 |
*** eolivare has quit IRC | 18:19 | |
hberaud | Ok thanks | 18:19 |
clarkb | I can try to ehlp too if you have links | 18:28 |
hberaud | clarkb: our issue is the both failing jobs there => https://zuul.opendev.org/t/openstack/builds?job_name=release-openstack-python | 18:46 |
hberaud | Our original issue was that the ussuri branches doesn't existed yet for the both project however we fixed that few days ago (https://review.opendev.org/c/openstack/releases/+/772995) and we reenqueued the failing jobs | 18:47 |
hberaud | I can see that the branches are now there | 18:47 |
hberaud | https://zuul.opendev.org/t/openstack/build/63f7d32d42c74d5f8b7484d48e42541e/log/job-output.txt#200 | 18:48 |
hberaud | sorry => https://zuul.opendev.org/t/openstack/build/63f7d32d42c74d5f8b7484d48e42541e/log/job-output.txt#201 | 18:48 |
clarkb | they both have the same issue: pbr is asserting a much larger version number is necessary based on its semantic versioning requierments | 18:48 |
hberaud | yes | 18:49 |
clarkb | (and consequently is refusing to build for the lower version number) | 18:49 |
hberaud | We was thinking that it was due to the missing branches | 18:49 |
clarkb | that is caused by annotations in commit messges saying there are breaking changes | 18:49 |
fungi | Error parsing /home/zuul/src/opendev.org/openstack/tripleo-ipsec/setup.cfg: ValueError: git history requires a target version of pbr.version.SemanticVersion(11.0.0), but target version is pbr.version.SemanticVersion(9.3.1) | 18:49 |
fungi | yeah, just saw that myself too | 18:49 |
clarkb | should be able to confirm that by looking at the git log between HEAD and previous release and then simply county up the version breaks | 18:50 |
hberaud | Sorry I need to eject for today, ttyt | 18:52 |
* hberaud afk | 18:52 | |
clarkb | os-collect-config HEAD is tagged 13.0.0 | 18:53 |
fungi | the current tip of stable/ussuri for openstack/tripleo-ipsec is tagged as 9.3.1, 10.0.0, and 11.0.0 and is also identical to stable/victoria and master | 18:53 |
clarkb | so pbr won't let you release 11.0.2 from that point | 18:53 |
clarkb | the 13.0.0 tag asserts breaking changes between it and 11.0.1 and so you cannot tag 11.0.2 there and respect semantic versioning | 18:54 |
clarkb | I want to say you can turn off semantic versioning in pbr? but maybe I am wrong | 18:54 |
fungi | which can probably only be done in the setup.cfg? which means a new commit, which won't be covered by those tags... | 18:58 |
clarkb | yes likely | 18:58 |
clarkb | hrm I'm not finding a way to turn it off in a quick grep of pbr | 18:59 |
clarkb | naively this relaese already exists and is published here: https://pypi.org/project/os-collect-config/13.0.0/ do we need an 11.0.2? | 19:01 |
clarkb | (basically pbr has encoded the answer to my question as "no do not do that") | 19:01 |
*** sboyron_ has quit IRC | 19:18 | |
fungi | yeah, these were in an unfortunate situation where they got their stable releases tagged on master because they never got around to branching for one or two releases in a row, was that basically it? | 19:21 |
*** bdodd has quit IRC | 19:29 | |
* hberaud back | 20:07 | |
hberaud | yes that's it | 20:09 |
clarkb | it seems that 11.0.2 is still trying to be tagged on master though | 20:10 |
clarkb | I think it would work if it was tagged on ussuri and 13.0.0 and 12.0.0 were not in history | 20:10 |
hberaud | so even if we propose 11.0.3 and 9.3.2 it won't help us, isn't? | 20:10 |
clarkb | as long as the newer tags are in the history of those tags then that is correct | 20:10 |
hberaud | where are new bum 11.0.3 & 9.3.2 | 20:11 |
clarkb | the problem is semver says you cannot have 13.0.0 and 11.0.2/11.0.3 on the same commit | 20:11 |
hberaud | ok I got | 20:11 |
hberaud | it | 20:11 |
clarkb | (and 13.0.0 can't come before 11.0.2 either) | 20:11 |
hberaud | make sense | 20:12 |
clarkb | it might make sense to check for these rules being violated before tagging things in CI | 20:12 |
clarkb | I expect this could be done by making the tag as proposed then attempting to build an sdist of it | 20:13 |
hberaud | locally | 20:13 |
clarkb | or in pre merge ci for the tag proposal | 20:13 |
fungi | yeah, so to restate, the error is effectively because we're trying to add a tag to a branch which is older than another tag already on that branch/in that branch's history? | 21:15 |
*** nweinber has quit IRC | 21:53 | |
*** jbadiapa has quit IRC | 22:03 | |
clarkb | fungi: the position on the branch of the tags matters too but yes | 22:06 |
fungi | er, right, we're basically trying to add out-of-order tags in a branch history | 22:09 |
*** gmann is now known as gmann_afk | 22:10 | |
*** abelur has quit IRC | 22:41 | |
*** abelur has joined #openstack-release | 22:41 | |
*** armstrong has quit IRC | 22:50 | |
*** slaweq has quit IRC | 23:09 | |
*** gmann_afk is now known as gmann | 23:11 | |
*** whoami-rajat__ has quit IRC | 23:43 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!