Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2021 Edition RFC #16

Open
nikomatsakis opened this issue Aug 5, 2020 · 20 comments
Open

2021 Edition RFC #16

nikomatsakis opened this issue Aug 5, 2020 · 20 comments
Assignees
Labels
A-initiative Initiative the team is working on M-triage Topic for the Core Team weekly triage meeting

Comments

@nikomatsakis
Copy link
Contributor

I just figured I'd add this as a reminder to check in on the 2021 Edition RFC regularly rust-lang/rfcs#2966.

@nikomatsakis nikomatsakis added M-triage Topic for the Core Team weekly triage meeting A-initiative Initiative the team is working on labels Aug 5, 2020
@github-actions
Copy link

github-actions bot commented Aug 5, 2020

This issue is an item on the Core Team's public agenda, and the team will discuss it every week during the triage meeting. The goal of the issue is to provide a public record of our discussion, so only members of the Core Team are allowed to comment here.

Please get in touch with the Core Team by emailing core-team@rust-lang.org if you have something to add!

@github-actions github-actions bot locked and limited conversation to collaborators Aug 5, 2020
@nikomatsakis
Copy link
Contributor Author

2020-08-05:

Discussion seems to be centered about the question of how much to separate the "retrospective" (what has happened over the last N years?) from the "edition" (what migrations or new lints are required to use edition = X?)

Summary comment of alternative proposal and some further considerations.

@steveklabnik
Copy link
Member

today: just a general "hey check out this RFC, we'll have to decide on it eventually." Lots of comments!

@steveklabnik
Copy link
Member

Today: niko and I need to chat about the feedback we've gotten, stuff has died down

@steveklabnik
Copy link
Member

Today: no updates because there were too many things going on in the past week, niko and i are gonna sync up and present a plan next week

@steveklabnik
Copy link
Member

@nikomatsakis and I had a meeting about it, and he posted a comment on our behalf to get more information about some objections.

@steveklabnik
Copy link
Member

it has been a busy week. @nikomatsakis and i are gonna talk this week about moving forward.

@steveklabnik
Copy link
Member

We didn't talk about this this week, but we are trying to move things forward.

@Mark-Simulacrum
Copy link
Member

We also publicly committed to having this ready by October 15th (September 3rd + 6 weeks).

@steveklabnik
Copy link
Member

We talked async a bit, but didn't find a common time to chat yet. Soon!

@nikomatsakis
Copy link
Contributor Author

Update: still waiting on folks to review the RFC.

@steveklabnik
Copy link
Member

@ashleygwilliams has left a big review that @nikomatsakis and I need to read and respond to.

@Mark-Simulacrum
Copy link
Member

Niko and Steve plan to sync up later today or this week to make progress on this, but no progress just yet.

@Manishearth
Copy link
Member

Update from triage: Ashley's concerns mostly apply if this RFC is going to establish editions in general rather than specifically 2021, Niko to tweak the RFC to be 2021-specific and we can establish general edition guidelines in a mini RFC in the future.

(I do think the 2021 edition RFC establishes most important points of editions in general pretty well, but that just means that the general edition RFC can be mostly copy-paste)

@aidanhs
Copy link
Member

aidanhs commented Nov 18, 2020

Concern: learning from our experience is great but not good for end users (vs maintainers) - are they going to have to read 4 RFCs to understand 'editions'? Not a blocking concern, but our documentation around editions and edition definition needs investment. Ashley would be fine merging if it just applied to next year.

Niko/Steve provided additional context on intent: Ashley found this helpful, but didn't find it was communicated by the RFC
Proposal from Mark: "we do an edition next year" the end. Follow up with another RFC that defines the detail

Next steps: Niko/Steve/Ashley to talk separately.

@Manishearth
Copy link
Member

Update: Mark and others have been working on clarifying things

@aidanhs
Copy link
Member

aidanhs commented Dec 9, 2020

Work is continuing (Mark + others), Niko needs to update the existing RFC thread

@Manishearth
Copy link
Member

Manishearth commented Dec 16, 2020

Mark thinks there may be a consensus he can pin down in a draft.

@aidanhs
Copy link
Member

aidanhs commented Jan 6, 2021

Mark created this doc (for core team members only) with the headline "This document outlines a summary of the concerns and proposals on the table for editions in Rust, both with respect to a potential 2021 Edition and the future plans in general."

Mark is now going to arrange meetings with appropriate parties to define the next steps (since they're unclear).

@aidanhs
Copy link
Member

aidanhs commented Jan 19, 2021

Myself, @Manishearth and @nikomatsakis spoke to Mara last week about edition progress to get an idea of where things lie. We did not get a chance to speak to @Mark-Simulacrum (as a major stakeholder) and will schedule for this coming week. We don't have anything to present at Core team triage this week.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A-initiative Initiative the team is working on M-triage Topic for the Core Team weekly triage meeting
Projects
None yet
Development

No branches or pull requests

5 participants