They didn't ship 19 regressions over 2 weeks. "Merged" doesn't mean "shipped". Their customers have probably seen none of those because they've all been fixed.

Such a terribly bad faith take. I feel upset reading this more than I should have.

▲

SpicyLemonZest 2 days ago | parent | next [-]

On what basis do you say their customers probably didn't see them? I'm not intimately familiar with Bun, but I work with people who try to do software development in this way, and they routinely ship regressions to customers. They believe that this is because we're not AI-enabled enough, and if only we had the right loops they'd stop shipping bugs; I think that it's not about the loops and the bugs reflect their lack of understanding about what they're trying to do.

▲

throw1234567891 2 days ago | parent [-]

They told you, can’t you read? All 19 regressions were fixed before release.

▲

SpicyLemonZest 2 days ago | parent [-]

The source article says no such thing and at least one of them (https://github.com/oven-sh/bun/issues/31188) seems to have been publicly reported.

▲

scrollaway 2 days ago | parent | next [-]

It was fixed on May 21st, which is 6 days after it was merged to main, and is 6.5 weeks before the release.

▲

throw1234567891 2 days ago | parent | prev | next [-]

Because people cannot try open source software by building it themselves before release, right? No?

	▲	2 days ago \| parent [-]
		[deleted]

▲

nickv 2 days ago | parent | prev [-]

Dude, just give up and admit you misread the point in the most negative bad faith way possible.

▲

torginus 2 days ago | parent | prev [-]

Yeah, it sounds more like they found 19 regressions after the migration so far.