Conversation
Notices
-
Embed this notice
@lethe @arcana @sun_eater @hj not unheard of to have WIP features pushed to stable, especially if you want feedback from more people. I'll guess that the pleroma instances running on the develop branch are in the minority
-
Embed this notice
@lewdthewides @arcana @sun_eater >especially if you want feedback from more people
pretty much this. My QA process is something like this:
1. I make a MR and merge changes into my own "shigusegubu" branch, deploy it on titular instance and check how everything works and if I find any issues.
1.1. Even when I'm satisfied with changes I dogfood final version for a week or so.
2. MR gets merged into develop, I ask admins of few instances that I know run develop branch (including myself) to ask users to report any issues they find.
2.1. any issues found get fixed in separate follow-up MR
3. We get a new minor release, feature is pushed onto unsuspecting public.
3.1 Any outstanding issues get fixed in a point-1 release, possibly point-2 etc.
Remember if you scream about issues into void it will unlikely get fixed. If I or other developers follow you we MIGHT notice it but it still can get lost in sea of shitposts.
If you mention some devs i.e. me, I'll consider fixing it but I might forget.
If you make an issue it will be there and will get fixed.
So pick what chances you like.
-
Embed this notice
@hj @arcana @lewdthewides @sun_eater I am once again asking for bookmark folders
-
Embed this notice
@moth_ball @arcana @lewdthewides @sun_eater i'll look at MR today.