pull down to refresh

100 sats \ 3 replies \ @optimism 9 Jan \ parent \ on: How FOSS devs maintain their apps? devs

I mean as in release->a lot of breaks, not permanent broken.

Edit: before I left X, it had switches a couple of times (until they made "paid beta tester mode") where you could opt-in to new features. GitHub does this a lot too. "Frontier mode" sounds cool, lol. (But I can imagine it needing a lot of work)

write
preview
262 sats \ 2 replies \ @k00b 9 Jan

Ah, fair. That's always been our release process - a sort of communal final QA.[1]

It has been especially bad lately though. My mental map of SN got written to disk while we worked on wallets. I'm still rebuilding the index.

  1. On more than one occasion I recall @siggy47 saying to some new stacker "oh they probably broke that in the release, it'll get fixed soon" aka "these fucking guys ..." ↩

reply
100 sats \ 1 reply \ @optimism 9 Jan
It has been especially bad lately though. My mental map of SN got written to disk while we worked on wallets. I'm still rebuilding the index.

That's what I understood (hence the "maybe a phase?"). It's not criticism really - just something I noticed: basically that as you're moving fast, things get broken.

Perhaps the stacker populace is still too small to stage features through a switch; I'm not sure what scale is needed to effectively do it. There are a lot of power users on here though.

reply
100 sats \ 0 replies \ @k00b 9 Jan

I got you. I didn't mean to sound sensitive as much as I meant to be appropriately concerned. Our release process has no process so it's a good callout.

reply