HackMD
This Development-cycle in Cargo: 1.87
This is a summary of what has been happening around Cargo development for the last 6 weeks which is approximately the merge window for Rust 1.87.
Plugin of the cycle
Cargo can't be everything to everyone,
if for no other reason than the compatibility guarantees it must uphold.
Plugins play an important part of the Cargo ecosystem and we want to celebrate them.
Our plugin for this cycle is TODO
Thanks to TODO for the suggestion!
Please submit your suggestions for the next post.
Implementation
Design discussions
Misc
- Daily reports by Eh2406 on the progress of the Rust implementation of the PugGrub version solving algorithm
Focus areas without progress
TODO
How you can help
If you have ideas for improving cargo,
we recommend first checking our backlog
and then exploring the idea on Internals.
If there is a particular issue that you are wanting resolved that wasn't discussed here,
some steps you can take to help move it along include:
- Summarizing the existing conversation (example:
Better support for docker layer caching,
Change inCargo.lockpolicy,
MSRV-aware resolver
) - Document prior art from other ecosystems so we can build on the work others have done and make something familiar to users, where it makes sense
- Document related problems and solutions within Cargo so we see if we are solving to the right layer of abstraction
- Building on those posts, propose a solution that takes into account the above information and cargo's compatibility requirements (example)
We are available to help mentor people for
S-accepted issues
on
zulip
and you can talk to us in real-time during
Contributor Office Hours.
If you are looking to help with one of the bigger projects mentioned here and are just starting out,
fixing some issues
will help familiarize yourself with the process and expectations,
making things go more smoothly.
If you'd like to tackle something
without a mentor,
the expectations will be higher on what you'll need to do on your own.
