Lena
fa41a030b8
Sometimes bugs come back or are not fixed all the way. We want to preserve the context of the issue we've closed prematurely so instead of always making people open a new github issue in this case we want to be able to notice if someone* comments on a closed bug and decide what to do about it. Before: Bug is closed → A user can again/still reproduce it on a new version and leaves a comment → Maybe someone sees the notification about it, maybe not; maybe they see it but forget to act on it right away and it's lost. After: Bug is closed → A user can again/still reproduce it on a new version and leaves a comment → The issue is added to a project board where it's visible until someone makes a call about it (maybe the comment was “oh my glob i'm so happy this was fixed” and no action is needed, or maybe the issue must be reopened as a regression). *Someone in this case means (1) not a bot, (2) not a member of staff. Release Notes: - N/A
Zed
Welcome to Zed, a high-performance, multiplayer code editor from the creators of Atom and Tree-sitter.
Installation
On macOS, Linux, and Windows you can download Zed directly or install Zed via your local package manager (macOS/Linux/Windows).
Other platforms are not yet available:
- Web (tracking issue)
Developing Zed
Contributing
See CONTRIBUTING.md for ways you can contribute to Zed.
Also... we're hiring! Check out our jobs page for open roles.
Licensing
License information for third party dependencies must be correctly provided for CI to pass.
We use cargo-about to automatically comply with open source licenses. If CI is failing, check the following:
- Is it showing a
no license specifiederror for a crate you've created? If so, addpublish = falseunder[package]in your crate's Cargo.toml. - Is the error
failed to satisfy license requirementsfor a dependency? If so, first determine what license the project has and whether this system is sufficient to comply with this license's requirements. If you're unsure, ask a lawyer. Once you've verified that this system is acceptable add the license's SPDX identifier to theacceptedarray inscript/licenses/zed-licenses.toml. - Is
cargo-aboutunable to find the license for a dependency? If so, add a clarification field at the end ofscript/licenses/zed-licenses.toml, as specified in the cargo-about book.