15:00:12 <gagehugo> #startmeeting openstack-helm
15:00:13 <openstack> Meeting started Tue Jan 12 15:00:12 2021 UTC and is due to finish in 60 minutes.  The chair is gagehugo. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:16 <openstack> The meeting name has been set to 'openstack_helm'
15:00:21 <gagehugo> #link https://etherpad.opendev.org/p/openstack-helm-weekly-meeting agenda
15:00:23 <gagehugo> o/
15:00:26 <miniroy1> \o
15:00:42 <stevthedev> GM
15:01:16 <lamt> o/
15:03:22 <cliffparsons> \o
15:03:30 <reddy1> \o
15:06:30 <gagehugo> #topic OSH reno gate
15:06:48 <gagehugo> From last week's discussion, I put up a change here
15:06:50 <gagehugo> #link https://review.opendev.org/c/openstack/openstack-helm/+/769622
15:07:59 <gagehugo> The current direction of this has a yaml for each chart, with any updates to the chart requiring a bump also requiring an addition to the yaml for the corresponding chart
15:08:27 <gagehugo> likely just a short snippet about what changed in the version bump
15:08:30 <gagehugo> any thoughts?
15:09:41 <reddy1> does it mean it requires to bump the chart at two places for every commit?
15:10:44 <gagehugo> with this yes
15:11:14 <reddy1> to me it is too much to ask and too many changes
15:11:40 <gagehugo> I would like to have zuul notify a submitter roughly the same way it does with the current chart version bump
15:12:58 <gagehugo> reddy1: Do you have any suggestions for a possible alternative?
15:13:16 <reddy1> so with every commit, developer is expected to write version along with the change details?
15:14:11 <gagehugo> since we are now releasing charts publicly, we need to be documenting what has changed with each version release
15:14:53 <gagehugo> I do wonder if this could be automated somehow with zuul
15:15:14 <gagehugo> because it is a lot to ask devs to update a bunch of things
15:15:36 <reddy1> I do not have any better suggestion, just wondering about maintaining the version at two places
15:17:48 <gagehugo> I'll keep poking at it, maybe we can automate it somehow from the git commit
15:17:59 <reddy1> we can probably continue this and optimize it as we continue work this
15:18:08 <gagehugo> sure
15:19:00 <gagehugo> If anyone has any comments/suggestions later, please feel free to comment on the change
15:19:21 <gagehugo> #topic open discussion
15:19:28 <gagehugo> Floor is open if anyone has anything
15:23:24 <gagehugo> thanks everyone, have a good rest of the week!
15:23:26 <gagehugo> #endmeeting