Skip to content

Agenda: investigate releasing ready-made builds #19

@apiraino

Description

@apiraino

This is a bit of a problem across the Rust project.

  • Many of our tools internal tooling are written in Rust or use Rust tooling (and IMO sometimes that's not really necessary)
  • Being internal tools there is not a big push to release binaries. People are usually asked to clone the repo, compile and run (cargo-bisect-rustc is an exception)
  • Your workstation's disk is filled up with debug builds

So, I want to file a note here about how we can release binaries for some tooling, starting with the prioritization agenda (but each repository is a story by itself)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions