https://bugzilla.wikimedia.org/show_bug.cgi?id=38865
--- Comment #14 from Krinkle <[email protected]> 2012-09-21 16:17:42 UTC --- (In reply to comment #12) > (In reply to comment #2) > > This must not have any unresolved dependencies before a new wmf-branch is > > created and deployed. > > Rob, just to know: is this an actual decision or just a generic hope? > 1.20wmf12 has been deployed to all non-Wikipedia projects without resolving > blockers. en.wiki is scheduled for Monday and it's completely unclear what's > supposed to happen before and after such deployment. I'm not sure that is a question, if it is that is a problem. Though we already knew that. Obviously we do have the principle of blocking bugs. The question is where they are listed (in this case on this bug), and secondly it is important that before deployment stuff here doesn't have loose ends. We can't demand bugs to be fixed by just dumping them on this bug, what I think is a reasonable demand however is that there are no unresolved blockers at the deployment window. Meaning either they are fixed, or removed from the blocker list. But not ignored and let to rot, which is very frustrating but current practice (!). >From spending time in the office I know that's not the case they're not ignored. People do go over this blocker list and decide to either backport a fix, write a new patch or decide it is not important enough. The problem is that result is then not communicated back down to where it belongs: The bug itself and therewith the blocker list here. It can happen that a decision is made that a bug is not blocking enough, but then it should simply be removed as blocker (with a rationale in the bug comment) and either: * assigned to a person to work on soon after deployment * or if not important right now and no person available as assignee, put on a milestone for later (e.g. 1.20 release) * or if no milestone, adjust the overall priority. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
