| frickler | tkajinam: do you want to double-check the changes elodilles made on https://review.opendev.org/c/openstack/releases/+/910408 ? we could also proceed without that if you prefer | 06:43 |
|---|---|---|
| opendevreview | Elod Illes proposed openstack/releases master: Add 2024.2 Dalmatian deliverable files https://review.opendev.org/c/openstack/releases/+/915312 | 07:37 |
| vgvoleg | Hello everyone! can anyone help me with feature release with mistral-lib? | 07:50 |
| vgvoleg | elodilles: my friend, previously proposed approach with new-release throws an error with 0 details and I was not able to figure out what's wrong | 07:51 |
| vgvoleg | all I want is to create a new tag like 2.11.0 and that's it | 07:55 |
| vgvoleg | to unblock mistral development | 07:55 |
| elodilles | vgvoleg: i've just proposed the new 2024.2 Dalmatian deliverable files patch (see above), as soon as that have merged, you should be able to propose a mistral-lib release there | 07:59 |
| elodilles | assuming you want to release on master branch (2024.2 Dalmatian) as that is the current development branch where features can be merged | 08:01 |
| elodilles | vgvoleg: on the other hand, new-release command should work on every branch (that is still maintained) | 08:02 |
| elodilles | vgvoleg: on the other hand, new-release command should work on every branch (that is still maintained) | 08:03 |
| elodilles | maybe you can copy the terminal output to paste.opendev.org and show us, so that we might be able to help | 08:03 |
| vgvoleg | sorry, I was disconnected for some reason, were there any messages before "on the other hand..."? | 08:04 |
| vgvoleg | elodilles: https://paste.opendev.org/show/823784/ | 08:10 |
| vgvoleg | probably it is wrong to call it from mistral-lib repo directly | 08:10 |
| elodilles | vgvoleg: yepp, it should be called in 'releases' repository | 08:11 |
| vgvoleg | but overall, did I understand instructions correctly and my query is fine? xd | 08:12 |
| elodilles | should be: tox -e venv -- new-release dalmatian mistral-lib feature | 08:13 |
| elodilles | but for that, the above '2024.2 Dalmatian deliverable files' patch has to be merged | 08:14 |
| elodilles | so this should work soon :) | 08:14 |
| elodilles | release-team: please review this as soon as you have time, because there are folks, who are eager to release their deliverables ;) https://review.opendev.org/c/openstack/releases/+/915312 | 08:15 |
| frickler | I still want to call that directory 2024.2, I haven't seen any argument against that other than "tradition" | 08:17 |
| elodilles | and 'tools' o:) | 08:17 |
| frickler | tools can be fixed, that's not a reason to carry on with misleading and confusing notation | 08:21 |
| vgvoleg | elodilles: ok, you have my +1, but overall 2024.2 notation is better, it took couple minutes from me to figure out what name 2024.1 has | 08:24 |
| elodilles | indeed, though the release team decided to keep the 'name' as default id for cycles, and only use YEAR.COUNTER id on stable branches. so yes, we can call this tradition. (besides, marketing folks also use the 'name' as well). on the other hand we use usually like '2024.2 Dalmatian' to make it clear | 08:27 |
| ttx | Yes it is the tradition to consider that "Dalmatian" is the name of the development cycle leading to (what should ultimately be) the 2024.2 release.. I see no reason to break that tradition, especially as it would require a bunch of fixes in tools and processes and we just digested the previous series of changes | 11:21 |
| ttx | Happy to be overruled by the majority, though :) | 11:22 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!