Open dreeves opened 1 year ago
FAQ: What if I create a gissue myself and then resolve it myself?
Then you're good. You can both resolve and close. "Opener closes".
TODO: me elsewhere: "meta: avoid both closing and resolving unless it's your own gissue. Which this one technically was but then got assigned to other people"
Joel Spolsky in his classic post on Painless Bug Tracking:
AKA "opener closes". Here's what that evolved into in Beeminderland:
The check&balances protocol for closing&resolving gissues
Every closed gissue should get a label for why it was closed (fixed, nixed, duplicate, could-not-replicate, etc). However, to make sure the person who opened the gissue agrees and signs off on the resolution, the person resolving the gissue should either close it or add the resolution label but not both. Nudge the opener of the gissue to resolve it if you closed it or nudge them to close it if you resolved it. See the Quick Links in the README for closed-but-unresolved gissues.
If the list of closed-but-unresolved gissues grows without bound, then beemind it.
Cognata
195
41
Verbata: software engineering principles, gissue management, spolsky, opener closes,