| thuvh | hello, to deploy monasca, could you plz guide me what branches should be created? | 03:02 |
|---|---|---|
| *** bauzas_ is now known as bauzas | 03:32 | |
| *** bauzas_ is now known as bauzas | 04:06 | |
| frickler | thuvh: from the context I've seen on the mailing list and what gmann wrote earlier, I assume you want to release monasca, not deploy it? I don't see a new branch would be needed for the latter? | 05:22 |
| frickler | thuvh: regarding a new release, the new branch would be created by the release automation, no need to create a branch manually. but also it would be necessary to make sure that the CI for all monasca repos is working | 05:23 |
| frickler | this currently doesn't seem to be the case yet, in particular please check the zuul config errors at https://zuul.opendev.org/t/openstack/config-errors?branch=master&skip=0 related to monasca | 05:23 |
| frickler | the testing also needs to be updated to use the latest python versions that are to be supported globally by openstack, like python3.11 | 05:26 |
| thuvh | thank you, yep, I would like to release it. | 06:59 |
| thuvh | hi @frickler, I checked zuul config errors, I found that an error related to missing repo elastic/kibana (remove in https://github.com/openstack/project-config/commit/d05ca87e799d16976decafe74737578421f14541) | 07:05 |
| thuvh | is there any suggestion in this case? | 07:05 |
| frickler | thuvh: yes, you need to remove that repo from your job definition | 07:34 |
| opendevreview | Merged openstack/releases master: Release metalsmith for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923115 | 08:56 |
| opendevreview | Merged openstack/releases master: Release python-cloudkittyclient for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923132 | 09:01 |
| opendevreview | Merged openstack/releases master: Release python-barbicanclient for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923131 | 09:02 |
| opendevreview | Merged openstack/releases master: Release ovsdbapp for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923129 | 09:05 |
| opendevreview | Merged openstack/releases master: Release python-neutronclient for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923137 | 09:08 |
| opendevreview | Merged openstack/releases master: Release openstacksdk for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923116 | 09:13 |
| opendevreview | Merged openstack/releases master: Release sushy for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923140 | 09:28 |
| opendevreview | Merged openstack/releases master: Release python-manilaclient for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923136 | 09:31 |
| opendevreview | Merged openstack/releases master: Release python-ironicclient for Dalmatian-2 milestone https://review.opendev.org/c/openstack/releases/+/923133 | 09:31 |
| opendevreview | Merged openstack/releases master: Add missing release note links https://review.opendev.org/c/openstack/releases/+/922088 | 10:00 |
| thuvh | @frickler: so could I skip monasca-kibana-plugin and release other components in this cycle or release monasca in the next cycle? | 10:42 |
| *** thuvh1 is now known as thuvh | 11:02 | |
| frickler | thuvh: I don't know enough about monasca to tell if a partial release would be useful. I also don't know if that would be valid from a release-team point of view | 11:13 |
| *** gthiemon1e is now known as gthiemonge | 13:27 | |
| *** bauzas_ is now known as bauzas | 13:46 | |
| *** whoami-rajat_ is now known as whoami-rajat | 14:00 | |
| *** bauzas_ is now known as bauzas | 14:16 | |
| elodilles | gmann frickler thuvh: i've sent an answer to mailing list. i also don't know how useful is to release parts of monasca deliverables, it might be OK to release some monasca deliverables as '_independent' (thus, no part of 2024.2 Dalmatian coordinated release) | 14:21 |
| elodilles | release-team: opinions? ^^^ | 14:21 |
| elodilles | (hmmm, it's interesting that i don't see here my mail: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack.org/ ) | 14:24 |
| frickler | elodilles: did you send from an unsubscribed address? might be held in moderation (aka waiting for fungi), then | 14:25 |
| elodilles | frickler: nope, I sent it from my regular mail address, where i send the countdown mail from | 14:26 |
| elodilles | ahh, 'The message is larger than the 40 KB maximum size' | 14:28 |
| elodilles | :/ | 14:28 |
| fungi | elodilles: approved | 14:29 |
| elodilles | thanks fungi o/ | 14:29 |
| fungi | that rule catches a lot of spam spoofed to originate from subscriber addresses, but also serves as a subtle reminder to trim quoted material to just the comments you're responding about (and also not to top-post) | 14:30 |
| fungi | https://wiki.openstack.org/wiki/MailingListEtiquette | 14:31 |
| elodilles | ACK, thanks for the reminder o:) | 14:31 |
| clarkb | fungi: and also to write plain text email | 14:47 |
| clarkb | html email grows much more quickly in size. Plain text is far more manageable and handles quoting and threading much better | 14:47 |
| fungi | yes, the bulk of the message size is a very inefficiently created translation of the plain text into html. it doesn't even seem to try to save on message size | 14:48 |
| clarkb | right that particular email is basically double the size it needs to be because it has both plain text and html and the html version is very plain text like | 14:48 |
| *** bauzas_ is now known as bauzas | 15:27 | |
| *** haleyb is now known as haleyb|out | 21:18 | |
| *** bauzas_ is now known as bauzas | 23:43 | |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!