1 IRC_meeting_2022 08 09

John Johansen edited this page 2022-08-09 18:56:28 +00:00

(11:01:48 AM) cboltz: meeting time ;-)
(11:02:41 AM) ***georgiag is here
(11:03:16 AM) sarnold: ahoy
(11:03:21 AM) ***jontourville is here
(11:03:43 AM) jjohansen: hey, can you give 5 minutes
(11:04:48 AM) ***das_j is here
(11:14:09 AM) jjohansen: alright, I am back
(11:14:37 AM) jjohansen: cboltz, georgiag, jontourville, sarnold, anyone else: meeting time
(11:14:58 AM) sarnold: \o/
(11:15:15 AM) ***cboltz hides
(11:17:54 AM) jjohansen: oh well then without cboltz here I guess we can't have a meeting
(11:17:59 AM) jjohansen: :-)
(11:18:13 AM) cboltz: ;-)
(11:19:19 AM) jjohansen: we don't have anything listed on the meeting agenda, so I am going to start with releases
(11:20:08 AM) jjohansen: v3.0.7 - is out, hopefully it is the last one for a while, it was specifically to address the arch build issue where 3.0.6 was the debian
(11:20:09 AM) kron [~weechat@dslb-002-206-093-239.002.206.pools.vodafone-ip.de] entered the room.
(11:20:41 AM) jjohansen: v2.13.7 - is being worked on and will likely be this weekend
(11:20:49 AM) cboltz: hehe, I know I asked for doing releases more often - but monthly would be enough for me ;-)
(11:20:57 AM) jjohansen: hahaha
(11:21:38 AM) jjohansen: yeah, not planning on repeating if I can help it, but a monthly or every two month point release would be good
(11:22:16 AM) cboltz: just wondering - is doing releases more often easier/faster for you?
(11:22:53 AM) cboltz: or is the overhead for a "just one fix" release similar to a release with many changes?
(11:22:57 AM) jjohansen: also at this point 2.13 is not going to get monthly releases, if we do those. It would be more like every 6 months unless there is something really important
(11:23:07 AM) ghost_rider[m] left the room (quit: Server closed connection).
(11:23:10 AM) ghost_rider[m] [~ghostride@2001:470:1af1:101::6751] entered the room.
(11:23:12 AM) jjohansen: its inbetween
(11:23:58 AM) jjohansen: the release notes take more work than they should, we need to work on automating them more but, just pulling straight from the logs isn't going to work
(11:24:22 AM) jjohansen: unless everyone follows fixed commit formats and fixed merge styles etc
(11:24:43 AM) jjohansen: its just not going to happen, but the tooling around it can be improved
(11:25:06 AM) jjohansen: so a single issue release doesn't have a lot of release notes to dig through, so that part is less
(11:25:17 AM) kron_ left the room (quit: Ping timeout: 480 seconds).
(11:25:19 AM) jjohansen: the other end of things is kind of a fixed cost
(11:25:38 AM) jjohansen: and we need to cleanup and automate that end as much as we can too
(11:26:43 AM) sarnold: would it make sense to ask merge requests / patches / etc to add a blurb to a changelog file?
(11:26:45 AM) jjohansen: part of it is we need to figure out how to do a few things in gitlab that we currently doing in lp
(11:27:02 AM) jjohansen: that would let us drop the lp things which would cut out half the work
(11:27:51 AM) jjohansen: and if we could automate the announcements, so that the tweet, the email, the lp announcement, the web announcement aren't all different and have to be done separately
(11:28:00 AM) jjohansen: well that would cut out a lot of work
(11:28:08 AM) jjohansen: sarnold: no
(11:28:18 AM) jjohansen: it just won't happen consistently
(11:28:46 AM) cboltz: with the things you do in lp, do you mean creating the tarballs with prebuilt documentation etc., or something else?
(11:28:47 AM) sarnold: can we get gitlab to nag-o-bot about that?
(11:28:50 AM) jjohansen: asking one of contributors to do that is as much work or more than doing it ourselves ...
(11:29:05 AM) jjohansen: cboltz: that is part of it
(11:29:14 AM) jjohansen: also the signing of tarballs
(11:29:53 AM) jjohansen: which isn't exactly in lp, but it provides a way to attach the signatures
(11:30:13 AM) jjohansen: when we initially tried dropping lp, that was complained about immediately
(11:31:28 AM) cboltz: yeah, shipping security-related software without a gpg signature scares people ;-)
(11:31:46 AM) jjohansen: so if anyone wants to dig into those bits it would make me happy
(11:32:45 AM) jjohansen: so back to releases
(11:32:45 AM) jjohansen: v2.12.4 and v2.11.4 are both also a wip and are planned to be the last releases in those series (End of Life)
(11:33:02 AM) jjohansen: the next feature release will be this fall
(11:33:32 AM) jjohansen: I was hoping for September but I think realistically we are looking no earlier than october
(11:33:55 AM) jjohansen: well, caveat
(11:34:19 AM) jjohansen: we could roll a 3.1 release this month
(11:34:34 AM) jjohansen: it would be missing much of what we wanted to land
(11:35:02 AM) jjohansen: and then we could land the major feature release later in the year
(11:35:15 AM) jjohansen: the plan for the larger feature release is to call it 4.0
(11:35:51 AM) jjohansen: as there will again be lots of changes for policy to break older userspaces, and genprof/logprof
(11:35:52 AM) jjohansen: :)
(11:36:19 AM) jjohansen: don't worry cboltz, we will label every thing that breaks the tools as preview or experimental
(11:37:33 AM) jjohansen: I would like tool support, but I would rather get a release out the door this year, if people have to wait on me to add tool support it might take another year :)
(11:37:59 AM) jjohansen: or lets be honest many, many more :-D
(11:38:10 AM) cboltz: as long as the tools "just" don't support a new feature (but don't totally break), I'm fine
(11:38:16 AM) cboltz: given the usual delays, I vote for doing the 3.1 release this month
(11:38:32 AM) jjohansen: okay, we will look at doing that
(11:38:42 AM) cboltz: BTW: do you remember the originally planned release date for 3.1?
(11:39:05 AM) jjohansen: cboltz: there is nothing planned that is required, so only break the tools if a feature is used
(11:40:23 AM) jjohansen: cboltz: I don't have time for archaeology, or lets be realistic paleontology
(11:40:59 AM) cboltz: ok, I'll give you the answer ;-)
(11:41:15 AM) cboltz: <jjohansen> 3.1 will be out in the fall
(11:41:21 AM) cboltz: you said that in March 2019 ;-)
(11:41:25 AM) jjohansen: yeah
(11:41:38 AM) jjohansen: that was the plan, so easy to fall behind
(11:42:47 AM) cboltz: well, at least you wrote "in the fall" and not "this fall" back then ;-)
(11:43:03 AM) jjohansen: okay, if you have something that should be in the 3.1 release this month, please ping someone who can get it merged asap
(11:43:20 AM) jjohansen: so we are right on schedule \o/
(11:44:20 AM) cboltz: I'd say check the open MRs that are not older than a month or so - and then do the release
(11:44:27 AM) jjohansen: it would have been so embarrassing to have spring release
(11:44:47 AM) cboltz: ;-)
(11:44:52 AM) jjohansen: cboltz: certainly, just saying if there is anything else ...
(11:45:11 AM) cboltz: not from me
(11:45:30 AM) jjohansen: alright lets move on, does anyone have anything else to discuss
(11:46:58 AM) cboltz: maybe my little feature request from an hour ago - some pivot_root examples in simple_tests
(11:47:23 AM) cboltz: if someone types some examples in IRC, they might magically end up as a MR ;-)
(11:48:02 AM) jjohansen: cboltz: ack, I will at least a few done this week, and try to get a MR together for 3.1 with some man page improvements
(11:49:58 AM) jjohansen: well if there is nothing else
(11:50:02 AM) jjohansen: meeting adjourned