From Fedora Project Wiki
< Changes
(start the basic change details) |
|||
| Line 63: | Line 63: | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
Developers can begin using the Rust language in their projects. In the Stack Overflow Developer Survey 2016, Rust topped the list of [https://stackoverflow.com/research/developer-survey-2016#technology-most-loved-dreaded-and-wanted Most Loved] languages. | |||
Packagers can begin adding programs written in Rust to Fedora. For instance, Mozilla is starting to [https://hacks.mozilla.org/2016/07/shipping-rust-in-firefox/ use Rust in Firefox], and now Fedora's Firefox maintainers could enable those components. | |||
<!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | <!-- What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new functionality, what capabilities does it bring? Why will Fedora become a better distribution or project because of this proposal?--> | ||
Revision as of 22:36, 12 July 2016
Rust Compiler
Summary
Introduce packages for the Rust compiler and its Cargo build system.
Owner
- Name: Josh Stone
- Email: jistone at redhat dot com
- Release notes owner:
Current status
- Targeted release: Fedora 25
- Last updated: 2016-07-12
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Benefit to Fedora
Developers can begin using the Rust language in their projects. In the Stack Overflow Developer Survey 2016, Rust topped the list of Most Loved languages.
Packagers can begin adding programs written in Rust to Fedora. For instance, Mozilla is starting to use Rust in Firefox, and now Fedora's Firefox maintainers could enable those components.
Scope
- Proposal owners: Get rust and cargo into Fedora, and maintain them in the future.
- Other developers: N/A (not a System Wide Change)
- Release engineering: N/A (not a System Wide Change)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Cargo may be a stretch, then just delay that until later.
- If Rust fails too, just don't ship anything now.
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), No
- Blocks product? None
Documentation
N/A (not a System Wide Change)