Re: git: bdc30d59c158 - main - lang/go12*: Update to 1.26.8 and 1.27.1
- Reply: Adam Weinberger : "Re: git: bdc30d59c158 - main - lang/go12*: Update to 1.26.8 and 1.27.1"
- Reply: Dag-Erling_Smørgrav : "Re: git: bdc30d59c158 - main - lang/go12*: Update to 1.26.8 and 1.27.1"
- In reply to: Dag-Erling_Smørgrav : "Re: git: bdc30d59c158 - main - lang/go12*: Update to 1.26.8 and 1.27.1"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 03 Sep 2026 13:20:25 UTC
On Thu, Sep 3, 2026 at 3:58 AM Dag-Erling Smørgrav <des@freebsd.org> wrote: > > Dag-Erling Smørgrav <des@FreeBSD.org> writes: > > Adam Weinberger <adamw@FreeBSD.org> writes: > > > lang/go12*: Update to 1.26.8 and 1.27.1 > > Do you think maybe you could have coordinated with me? > > To elaborate: this was done incorrectly. > > First of all, you updated both ports in a single commit instead of > updating them separately. This makes merging to quarterly needlessly > difficut since 1.27 does not exist on quarterly. Secondly, you did not > merge to quarterly. Third, you did not deprecate 1.25 as planned. You really wanted this discussion in public? Okay... 1. I don't recall being coordinated with on the last few rounds of 1.25/1.26 updates or adding Go 1.27. I'd be thrilled if you sent me an email ever saying "Let's plan the next step." I appreciated the discussion regarding planned deprecation in the recent 1.26-as-default PR, after I initiated the discussion. (Though it included 2. I did not find that the changes in 1.26 warranted an MFH so I did not do so. I'm pretty conservative about MFHs. 3. The fact that 1.27 does not exist in 2026Q3 is a great point and I agree it would have been better to separate the commits for that reason. 4. True. I did not deprecate 1.25. I did the updates in the middle of the night because I couldn't sleep, and that didn't feel like the right time to start the deprecation and exp-run cycle. 5. People who know you IRL say that they enjoy your company and that you are a respectful person. I'm not sure whether FreeBSD is an outlet for for some pent-up feelings or something, but come on, man. I work here too. We're on the same team. I care about Go, and I put in a lot of work to get it rolling again once it'd been abandoned. We all know how much better you are, so I'm not sure what else you're proving. You choose the way you speak to people, des, and you haven't given me much reason to be excited about writing an email to you to coordinate. I'm looking back to find an email reply from you that isn't wholesale rejecting an idea, or telling me that I did something wrong because you'd have done it differently. I haven't found it yet. Not even "try X instead" or something, just "no that's bad." It's exhausting. So I'm sorry, but, "Do you think maybe you could have coordinated with me" is hard to reply to, because I need to stop laughing first. "Coordinating" with you means emails written like the above. -- Adam Weinberger adamw@adamw.org // adamw@FreeBSD.org