[wp-trac] [WordPress Trac] #24771: Login can be blocked if primary_blog is set to a blog the user no longer belongs to that is marked as spam

[WordPress Trac]

#24771: Login can be blocked if primary_blog is set to a blog the user no longer
belongs to that is marked as spam
-----------------------------------+---------------------
 Reporter:  westi                  |       Owner:  nacin
     Type:  defect (bug)           |      Status:  closed
 Priority:  normal                 |   Milestone:  3.7
Component:  Multisite              |     Version:  3.5.2
 Severity:  normal                 |  Resolution:  fixed
 Keywords:  has-patch needs-codex  |
-----------------------------------+---------------------

Comment (by DrewAPicture):

 Replying to [comment:7 brianhogg]:
 > How does updating the codex for a future feature/change work - do we add
 an update before it's released or queue it somehow for after?

 Sometimes we edit it whenever the change is made, and sometimes we just
 mark `needs-codex` for future reference when we do the codex sprint for a
 new release.

 When the new Code Reference is in place and auto-parsing docblocks in the
 source, there will be less/no need for adding the `needs-codex` keyword
 and more emphasis on providing complete inline documentation.

 So in the case of this ticket, we would wait, though I anticipate the Code
 Reference will be in place (hopefully) before we do the 3.7 codex sprint.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/24771#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software