Confirmed users
3,376
edits
Community:SummerOfCode16:Brainstorming: Difference between revisions
Community:SummerOfCode16:Brainstorming (view source)
Revision as of 17:28, 22 March 2016
, 22 March 2016→Automation & Tools: - new project
(→Firefox: Not that the suggestion has already been added to the Community summerofcode16 page) |
(→Automation & Tools: - new project) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 280: | Line 280: | ||
! Mentor(s) | ! Mentor(s) | ||
! Comments | ! Comments | ||
|- | |||
! Debugging failures seen in CI Infrastructure | |||
! there are many things we can do to make the developer experience better when investigating a test job. From retriggering a job to collecting verbose logging or profiling data, to using a 1 click loaner to not only reproduce but to debug and fix issues, there are many parts of the CI system that we can make small improvements upon to simplify and make dealing with test jobs in CI more enjoyable. Full details available [https://docs.google.com/document/d/1kiTt79hnqP65UDYobm0ekYV27-0nRE9IDo9AB8NkSLQ/edit here] | |||
! python, javascript | |||
! Joel Maher | |||
! Joel Maher | |||
! | |||
|- | |- | ||
|} | |} | ||
| Line 422: | Line 429: | ||
! Mentor(s) | ! Mentor(s) | ||
! Comments | ! Comments | ||
|- | |||
| SemVer policy checker | |||
| Rust's library ecosystem works with "semantic versioning" (semver), which allows the version numbers of libraries to signify backwards-compatibility constraints. Roughly speaking, if your code works with version `X.Y` of some library, it should work with `X.(Y+1)` -- a new "minor release" -- as well. | |||
In practice, actually ensuring compatibility is quite subtle, and in Rust, there are some library changes that could theoretically break client code, but which we want to allow anyway. Our full stance on semantic versioning is written up in an RFC: https://github.com/rust-lang/rfcs/pull/1105 | |||
The goal of this project is to build a tool that can tell whether a set of changes to a library is valid under Rust's semver rules. Building this tool will likely require some hacking on the compiler itself (to produce the necessary information), and will hopefully result in some reusable infrastructure that can be applied to other projects as well. | |||
| Familiarity with Rust | |||
| Aaron Turon | |||
| Brian Anderson, Aaron Turon | |||
| | |||
|- | |- | ||
|} | |} | ||