Skip to content

Tracking issue for udp_peer_addr #59127

Closed

Description

@LinusU

Tracking issue for making peer_addr() on UdpSocket stable: #59106, #59104

Activity

  1. sanxiyn commented on Mar 13, 2019

    @sanxiyn
  2. added
    T-libs-api[DEPRECATED; DO NOT USE]
    B-unstableBlocker: Implemented in the nightly compiler and unstable.
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    on Mar 13, 2019
  3. jonas-schievink commented on Mar 13, 2019

    @jonas-schievink
  4. MOZGIII commented on May 1, 2019

    @MOZGIII
    Contributor

    How about moving this to stable?

  5. ghedo commented on Jun 7, 2019

    @ghedo
    Contributor

    What's left to do to stabilize this feature? Any ETA?

  6. Thomasdezeeuw commented on Jun 13, 2019

    @Thomasdezeeuw
    Contributor

    Can this be stablised for 1.37?

  7. Dylan-DPC-zz commented on Aug 24, 2019

    @Dylan-DPC-zz

    @rust-lang/libs any updates?

  8. sfackler commented on Aug 24, 2019

    @sfackler
    Member

    @rfcbot fcp merge

  9. rfcbot commented on Aug 24, 2019

    @rfcbot

    Team member @sfackler has proposed to merge this. The next step is review by the rest of the tagged team members:

    No concerns currently listed.

    Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up!

    See this document for info about what commands tagged team members can give me.

  10. added
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.
    on Aug 24, 2019
  11. rfcbot commented on Aug 30, 2019

    @rfcbot

    🔔 This is now entering its final comment period, as per the review above. 🔔

  12. added
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    and removed
    proposed-final-comment-periodProposed to merge/close by relevant subteam, see T-<team> label. Will enter FCP once signed off.
    on Aug 30, 2019
  13. added and removed
    final-comment-periodIn the final comment period and will be merged soon unless new substantive objections are raised.
    on Sep 9, 2019
  14. rfcbot commented on Sep 9, 2019

    @rfcbot

    The final comment period, with a disposition to merge, as per the review above, is now complete.

    As the automated representative of the governance process, I would like to thank the author for their work and everyone else who contributed.

    The RFC will be merged soon.

  15. added a commit that references this issue on Oct 6, 2019
    019b5b5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    B-unstableBlocker: Implemented in the nightly compiler and unstable.C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCT-libs-api[DEPRECATED; DO NOT USE]disposition-mergeThis issue / PR is in PFCP or FCP with a disposition to merge it.finished-final-comment-periodThe final comment period is finished for this PR / Issue.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions