Core team meeting 2016-01-05 (RFC 1214; FAQ; backcompat issues)

aturon · 2016-01-06T21:45:24.082Z

rust-lang/meeting-minutes/blob/master/core-team/meeting-2016-01-05.md

# Core team 2015-01-05

# Agenda

- PERMANENT ITEMS:
    - review subteam FCPs

        RFCs: https://github.com/rust-lang/rfcs/pulls?q=is%3Aopen+is%3Apr+label%3Afinal-comment-period

        Ungating: https://github.com/rust-lang/rust/issues?q=is%3Aopen+is%3Aissue+label%3AB-unstable+label%3Afinal-comment-period


* RFC 1214 (nmatsakis)
* Assorted trademark issues (aturon)
* FAQ review planning (brson, aturon)
* Backcompat issues (pcwalton)
* PR reviewing backlog (aturon)
* One-off contributors (aturon)

# RFC 1214

This file has been truncated. show original

bluss · 2016-01-07T13:19:20.619Z

The RFC 1214 situation seems fine, only a few crates have failed to upgrade. Leaving inactive crates behind is inherent in the decision to apply breaking changes. The oauth2 crate with the most impact is likely to be fixed ASAP, right?

Edit: It was fixed in december.

matthieum · 2016-01-14T18:06:48.548Z

The log issue mentionned (having multiple versions of the log crate, only one version allows logging and all software linked to the other does not log any longer) is quite painful. Is it an issue of symbol collision?

sfackler · 2016-01-14T18:27:49.913Z

@matthieum it’s almost the opposite, actually. The two log libraries are totally independent, and only one gets configured with a logger.

aturon · 2019-03-25T08:25:38.907Z

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.