gleam-lang/gleam

`gleam export otp-release` command

Open

#4,978 建立於 2025年9月15日

在 GitHub 查看
 (19 留言) (9 反應) (0 負責人)Rust (21,417 star) (960 fork)batch import
discussionhelp wanted

描述

I thought we had an issue for this, but I couldn't find one!

Our current "erlang-shipment" is a poor imitation of a proper OTP release. Create a new command that creates these, and then we can deprecate the erlang-release command.

Documentation: https://www.erlang.org/doc/system/release_structure

Distillery has some nice info here: https://hexdocs.pm/distillery/2.0.0-rc.8/understanding_releases.html

Karlsson has some information here on OTP applications: https://github.com/karlsson/glite

貢獻者指南

技術棧
rust
領域
cli
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Knowledge of Erlang/OTP releasesFamiliarity with Gleam compiler codebaseRust programming
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
Start by reviewing the linked Erlang documentation on release structure and the existing `erlang release` command in the Gleam codebase (likely in `src/`). Examine comment discussions for additional requirements. Then design the new `otp release` command, considering how to integrate with the current build system.