#releasing v0.3.14

1 messages ยท Page 1 of 1 (latest)

dull basin
#

summarizing the conversation after this msg: the feature flag works, but the fix doesn't, but the issue might not affect many people; still investigating

update: issue tracked down to MTU mismatch between docker bridge network and the 'real' network

#

releasing v0.3.14

random berry
#

ouch. Good ol MTU. What was it set to?

jagged totem
#

Ping me when you are ready to do it @dull basin . I am keen on trying out some ideas regarding PR tags & better release notes. Follow-up to #1079728730055921694 message

dull basin
random berry
#

Oh, it was the discussion with morlay?

dull basin
#

yup!

jagged totem
twin plume
#

I need to rebase that real quick and we can merge.

dull basin
#

@jagged totem I hesitated since the scope of the breakage seems somewhat limited now and I'm working on an actual fix, but we can just ship anyway, always good to get more reps in ๐Ÿ˜›

#

will wait for the go-ahead from @twin plume ๐Ÿ‘

jagged totem
#

If we don't need to rush anything out, then we can wait a few more days. Fridays make great release days :D. That will also give me time to make progress with a bunch of things (Mondays & Tuesdays are by design full of interrupts for me).

dull basin
#

yeah not sure. so far only two users seem to be affected. it could also be nice to get more folks trying it and noticing breakage; it's a bit more turbulent but probably more feedback than we'd get with making it opt-in, and it could make for a better v0.4.0. ๐Ÿค”

#

have a meeting, will keep pondering; @warm geyser feel free to decide for us ๐Ÿ˜›

twin plume
dull basin
#

my first instinct is that it'd be nice if it just took the PR body to save redundancy, but I can see how that might have too much information. maybe we could standardize on keeping the first comment (the PR "body") focused on release notes, and keep progress reports and TODO lists etc. in a separate comment, but maybe that's too disruptive