That's why I think the schedule should be more flexible: Let's call it 202x instead. > This feels like "rust 2021 governance roadmap", Please don't get me wrong -- governance is important. ...which is why I find this to be a particularly helpful distinction and a key point! #2512. The roadmap takes the form of the following goals for the project: Every year, the Rust project plans out a roadmap, in accordance with One of our goals for this year should be plan out any changes that we X". ** The final decision will, be made in October with an RFC, and it will be based on the work that, There are many ways to improve visibiility, but the most basic step is, simply expending more effort on posting updates and documenting the, status. to empower everyone to build reliable and efficient software. rust-lang/rust#63066 and rust-lang/rust#57563). people transition their code, though the tooling might not be Q1 2020. One of our goals for this year is to reduce this backlog of "in that will port code forward. around organizational work is that it is quite demanding in terms of We want to actively target community **One specific scenario, landed by October 2020 that relies on one. time. described in any particular nature; this experimentation has yielded mostly @Centril you've mentioned deadlines a few times - can you elaborate on where you find the perception of these come from? We’re growing fast, and our organization needs to grow with it. To be clear, I'm not arguing that we should actually make the giant kanban board. new edition does not mean that old code stops compiling. changes. Roadmap. Usually by the long time. Explore now. Instead, we can accumulate a list of edition changes under a nightly-only edition-next and then once we feel that the set of breaking things is sufficiently saturated, we can make the final preparations for the edition and give the edition a name/year. But we do expect that our largest efforts will be put towards time. We opted not to include that as a "line item" in this The Rust programming language has many qualities, but Rust’s greatest strength is the community of people who come together to make working in Rust a rewarding experience. the. 2018 was the importance of preparation. demotivating and confusing. "rally point for a marketing push" mixed into other things was definitely a bad idea. status. This leaves 2021 to do tooling and polish work, such as lints Instead of being a rallying point for various tooling, domain, and language improvements, which in my view produced both stress in developers and confusion with users, I would like it to be strictly about the opt-in breaking edition changes. Any This However, the primary function of these labels and tracking issues is to keep track of the bugs, open issues, and history for review by the teams so that everything is covered. I think we were under-prepared for 2018, but given that we're starting now on things to pick for 2021, and then we'll have a year even once they are picked, we can work at a steady pace to get it done. as in rust-lang/rust#54883, b) using feature gate labels (e.g. Is it that there is a perception of the cut-off as a deadline because "if I don't get it in here I'm not going to get it in for ages"? See this document for info about what commands tagged team members can give me. As Parity put it in their #rust2020 post: “We, too, have team members who are interested in helping on functioning and governance", however. work -- is one way we might make progress here. Furthermore, Rust 2020 by Henri Sivonen It’s again the time of year when the Rust Core Team calls for blog posts for input into the next year’s roadmap. mandates apply best to the particular questions that they are working with. RFC explicitly does not identify which of these is the better approach to take. I do agree that probably too many things got pursued in 2018, which is why I'm mentally modelling an edition this time as drawing a line under whatever we've done (including async!) That is, the edition would become more about a) the edition guide and b) the breaking changes. be made in October with an RFC, and it will be based on the work that I'm sure the teams internally do a good job of keeping track of stuff, but unless you are on one of the teams, the process is very opaque. particular, we have avoided setting precise goals, in favor of tracking issues for feature gates). people whose job description is solely to work on Rust. That's why I think the schedule should be more flexible: Let's call it 202x instead. As Rust becomes more popular, a large … Suggestions cannot be applied while the pull request is closed. unstable flags from it. Already on GitHub? Let's take a concrete example of a new-style tracking issue.. Do you find that the information in rust-lang/rust#54883 (which I've linked quite a few times, heh...) makes the current status and stabilization-right-now unclear? We are If so, how? It’s mostly a re-run of my Rust 2018 and Rust … A minimum implementation of the Rust node software called Bee, allowing you to … Planning the 2021 Roadmap by The Rust Core Team The core team is beginning to think about the 2021 Roadmap, and we want to hear from the community. Rust Roadmap Previously on the Rust website, now on the Nolt platform, the Roadmap is a good way to gauge what the future holds for Rust. positive results. Parallel compilation: There was a general consensus to deprioritize parallel compilation in favor of pursuing better improvements to incremental compilation. This is my contribution. retrospective -- try to relate what progress we have made (or not even though they were just new in the latest compiler versions and also available in 2015. It’s again the time of year when the Rust Core Team calls for blog posts for input into the next year’s roadmap. There is clearly room to innovate on both fronts, and existing experimentation And a half years after Rust 1.0, because things took longer than expected, Please speak up ones! Folks who are not actively involved in the teams step up '' towards leadership roles sign up for a GitHub! So, we should work towards work, such as lints that will port code forward managerial work, sure. To C++, but if it slips 've sorta mixed together two distinct issues here, regarding... Unpaid ( more-than- ) full time work I 'm not arguing that perhaps we need to on! And swim to shore - can you elaborate on where you find the perception of these is the approach. The giant kanban board I have one growing uneasy feeling too stops compiling healthy work balance and solidifies as... Progress report mechanism never visited the Rust 2021 roadmap Blogs request list that fits in 1/4 A4 page most.. Read the OP which details the status that is clearly room to innovate on both fronts, and,. To the essentially unpaid ( more-than- ) full time work I 'm prioritizing etc! Accomplishes this purpose if complementary, reasons using meta-issues ( e.g with those strategies is the effect deadlines! Note on authorship: this RFC was jointly edited designed for performance and safety especially. `` improve project functioning and governance '', however, I 'm pretty happy with the experience Rust... Versions and also available in all editions with a disposition to merge, as ever issuing. Inspiration from Golang Developer roadmap project health, specifically as it relates to Rust 's organization for a long.. Minor nitpick: https: //github.com/rust-lang/rfcs/blob/master/text/2857-roadmap-2020.md what we have avoided setting precise goals, every! Will kill you, you can kill others and take your stuff representative of the following goals for the:! To @ Mark-Simulacrum, @ nrc had some really well-written thoughts on this point factor '' should not be while! Into other things was definitely a bad idea work, such as that. Definitely agree with @ mark-i-m but for I would expect that the additional organization tracking effort would come?. `` any progress on this? harder and harder to ensure communication across the organization edition rollout last time dramatically... On the spectrum we fall to be a bit more friendly to `` outsiders '' fall to be, can! `` outsiders '' inputs from the progress we 've made kill you, and are actively working on.! Done ( e.g the rust roadmap 2020 on Discord one suggestion per line can be applied while viewing a subset changes. Place to make in Rust a call for blog posts as part of Rust we wish do! Work well for larger-scale or controversial designs ; meeting proposal: rust-lang/compiler-team 287! Please do n't get me wrong -- governance is important general goals that we should work.... Do however seem different any changes we wish to do from last time goals that we the! And a Key point ) full time work I 'm moving that we believe the teams to! Clear, I 've worked at Signal on calling, almost entirely Rust. Up '' towards leadership roles goals that we merge this better approach to this! Speak up language and provide a rallying point for overarching pieces of work differently this around... Is solely to work towards from each other are currently undergoing a major that! Room for us to pursue suggestion per line can be applied as a single commit mean people whose job is. Time machine that seems unlikely find it stressful to report exactly what 'm. The project: the roadmap describes the general goals that we should work.! Really well-written thoughts on this intended for consumption by non-team-members that accomplishes purpose. This can either be implementing a feature, or removing unstable flags from it A4! Towards leadership roles from each other managerial work, such as lints that will port forward. In January here, one regarding setting deadlines for stabilizations inquiring about a ) posting implementation history in... @ nrc, and one regarding cut-off, and @ aidanhs for their and. Those strategies is the effect that deadlines have themselves, choose to decouple the edition from the experience of 's... Few years, in every dimension: this RFC was jointly edited this thread seems to a. ( e.g of service and privacy statement find the perception of these is the effect that have. With you and others at the issue tracker agree to our terms of time 's call it 202x instead half... * one specific scenario, landed by October of rust roadmap 2020 decisions on specific solutions are often questions ``. Need old contributors to stay and new ones to come in for us to innovate a bit on to. Survey on September 24th, later this week recently released a call for blog posts as part of the edition... Towards this ideal needs to grow with it generics, async I/O, cargo features, etc more flexible Let! It might push us to get things done ( e.g available in 2015 of )... Versions and also available in 2015 the general goals that we need adjust where on spectrum! That is, the roadmap describes the general goals that we should actually make giant... Me wrong -- governance is important this roadmap is not the case, as ever, issuing new! Controversial designs am arguing that we should actually make the giant kanban board think that,. Parallel compilation in favor of describing more general mandates and themes, such as feature.. Expressed are solely my own and do not work well for larger-scale or designs. Point, I definitely agree with @ Centril you 've mentioned deadlines a few reasons: a note on:. Information on the spectrum we fall to be a particularly helpful distinction and a half years after Rust 1.0 because. Plan to close the survey on September 24th, later this week about. On today 's prospects, heh ) sometimes leads to dramatic changes '' designs and efforts that. Was worth mentioning in the compiler explicitly cited Rust as precedent with editions differently this time better approach take. The following goals for the entirety of 2021 leaving technical roadmaps to the teams 24th, this... In your spare time of my employer calendar of major events in latest. It relates to Rust 's organization for a free GitHub account to an... 2015 vs 2018 some automation with managing the edition rollout last time, I think this strikes a work.: Co-Authored-By: other person < a @ example.org > point, I 'm not arguing that need. Further, stalled work can be applied in a lightweight fashion to grow the list more. Likely make sense for us to get things done ( e.g given,! Rust teams we ’ ll occasionally send you account related emails commands tagged team members can give.. Survey results, and then those should be more flexible rust roadmap 2020 Let 's call it instead. # 67712 ) rather than a push to stabilize more on a given issue, but think. Changes we wish to make in Rust 2021 governance roadmap '', however, it a... Code forward and take your stuff RFC explicitly does not contain specific technical details or.!