07:55 <borneoa_> PaulFertser: I'm ready for my usual weekend merge activity. Due to gerrit upgrade, what you think is best? Merging before the upgrade to avoid disruptions? Merging carefully after the upgrade and use this as test?

07:55 <PaulFertser> borneoa_: I would say merging through the Saturday and taking Sunday as a day off.

07:57 <PaulFertser> borneoa_: I can't say how much downtime it's going to be, especially due to potential OAuth issues (and github can be surprising too). If we're lucky, it'd be just about two hours. I'm trying to do testing migrations in advance but can't fully test it due to domain names and probably just missing something else too.

07:57 <PaulFertser> borneoa_: also the new system will have new versions of all compilers and cross-compilers used for Jenkins.

07:58 <borneoa_> PaulFertser: it wouldn't take much time. The patches I plan to merge are already queued in my local branch and tested for build.

07:59 <PaulFertser> borneoa_: on a bit related note, I remember sometimes submitting patches were producing build errors (as that's the nature of cherry-picking) but those were rare and promptly fixed, so in general I never worried much about it.

08:00 <borneoa_> PaulFertser: also, nothing really urgent to merge. I can wait for Sunday night or Monday. Then merge one by one to test also the external sync.

08:03 <borneoa_> PaulFertser: if you prefer, I let you run the merge during your own tests. The patches I plan to merge are in http://git.infradead.org/users/borneoa/openocd-next.git/shortlog/refs/heads/next

08:04 <PaulFertser> borneoa_: however you feel more comfortable with, really. You're doing so much work already. Guess something to "submit" will be handy for testing syncing etc, you're correct.

08:04 <borneoa_> PaulFertser: every commit in the next branch reports the number used by gerrit

08:05 <PaulFertser> borneoa_: btw, I'm experimenting with ccache, so far I see no reason why it shouldn't work to speed up the test builds.

08:06 <PaulFertser> And if someone asks why don't we just use free circleci or github ci or whatever other service I think the answer would be that we want to be capable of self-hosting critical infrastructure, and additional CI can be added if desired but not mandatory.

08:06 <PaulFertser> borneoa_: are you manually adding under-review-on tags? Or is this some smart gerrit integration system?

08:12 <borneoa_> PaulFertser: yes, ccache would help. I agree, holding the CI is an advantage. I'm only concerned about the additional work and data backup.

08:14 <borneoa_> PaulFertser: I use a script to cherry-pick from gerrit and it adds the tag.

08:14 <PaulFertser> borneoa_: btw, would you personally like to be able to reply to comments on Gerrit via e-mail?

08:16 <PaulFertser> borneoa_: as in https://gerrit-review.googlesource.com/Documentation/intro-user.html#reply-by-email

08:16 <PaulFertser> That's not the thing that I plan for this weekend but I hope to do it soon. Somehow Gerrit requires a local POP3 or IMAP4 server for that (nuts!).

08:28 <borneoa_> PaulFertser: around 10 years ago openocd migrated to gerrit. It was a stopper for me. I used to commute for few hours each day and I didn't mind doing patch review from my inbox during the long commute. But it was impossible to access gerrit during the travel, so end of involvements with openocd! I found later that there is a tool (don't remember the name) for working locally and sync later with a remote gerrit, but it didn't work

08:28 <borneoa_> straightforward and I dropped it. I don't know if this gerrit via email would have helped at that time, or if this can help other maintainers. I will check the link to understand better the review model

08:39 <PaulFertser> borneoa_: unfortunately it only works to reply to reviews it seems, not to review new patches afaict.

08:40 <PaulFertser> borneoa_: I'm ready to try researching this topic (reviews not requiring Internet connection) later when the dust settles.

08:44 <borneoa_> PaulFertser: not anymore urgent for me, but I will try to recover the name of the tool for offline review. Maybe in these 10 years it got easier to setup

08:47 <PaulFertser> borneoa_: no need, I'll be checking it later, probably there's something better now available.

13:45 <PaulFertser> 11 minutes CI with ccache now.