anomalyco/opencode
1
0
Fork 0
mirror of https://github.com/anomalyco/opencode.git synced 2026-07-22 10:15:31 -04:00
Code Issues 5.9k Packages Projects Releases 19 Wiki Activity

[FEATURE]: Better release cycles #2785

New Issue
Open
opened 2026-02-16 17:37:15 -05:00 by yindo · 1 comment
yindo commented 2026-02-16 17:37:15 -05:00
Owner
Copy Link
Copy Source

Originally created by @restray on GitHub (Nov 11, 2025).

Feature hasn't been suggested before.

  • I have verified this feature I'm about to request hasn't been suggested before.

Describe the enhancement you want to request

Hello world! 👋

First of all, thank you very much for all your amazing work on this project!

Issue Description

I’m subscribed to repository notifications for new releases, but I receive a lot of emails because there is a new release for every 2-3 bug fixes. This frequency is overwhelming, especially since many package managers (like Nix) struggle to keep up with this pace.

Proposal: Structured Release Cycles

To improve maintainability and reduce notification fatigue, I suggest adopting a more structured release cycle:

  • Fixes (0.0.x):
    Bundle bug fixes into a single release every Sunday evening. This way, users can start their workweek with the latest fixes, and package managers have a predictable schedule to follow.

  • Minor (0.x.0):
    Pin a dedicated GitHub issue listing all relevant improvements and features (with links to their respective issues). This makes it easier for new contributors to pick up tasks and ensures transparency about what’s included in each minor release.

  • Major (x.0.0):
    Reserve major releases for breaking changes or significant updates, ideally on an annual basis.

Why this approach?

  • Reduces email noise for subscribers.
  • Aligns with package manager update cycles.
  • Encourages community contributions by clarifying priorities.

Let me know what you think! I’m happy to help refine this further if needed.

Originally created by @restray on GitHub (Nov 11, 2025). ### Feature hasn't been suggested before. - [x] I have verified this feature I'm about to request hasn't been suggested before. ### Describe the enhancement you want to request # Hello world! 👋 First of all, thank you very much for all your amazing work on this project! ## Issue Description I’m subscribed to repository notifications for new releases, but I receive **a lot of emails** because there is a new release for every 2-3 bug fixes. This frequency is overwhelming, especially since many package managers (like Nix) struggle to keep up with this pace. ## Proposal: Structured Release Cycles To improve maintainability and reduce notification fatigue, I suggest adopting a more structured release cycle: - **Fixes (0.0.x)**: Bundle bug fixes into a single release every Sunday evening. This way, users can start their workweek with the latest fixes, and package managers have a predictable schedule to follow. - **Minor (0.x.0)**: Pin a dedicated GitHub issue listing all relevant improvements and features (with links to their respective issues). This makes it easier for new contributors to pick up tasks and ensures transparency about what’s included in each minor release. - **Major (x.0.0)**: Reserve major releases for breaking changes or significant updates, ideally on an annual basis. ## Why this approach? - Reduces email noise for subscribers. - Aligns with package manager update cycles. - Encourages community contributions by clarifying priorities. --- Let me know what you think! I’m happy to help refine this further if needed.
yindo added the discussion label 2026-02-16 17:37:15 -05:00
yindo commented 2026-02-16 17:37:15 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (Nov 11, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #4114: Similar concerns about release frequency from package maintainers (Nix) perspective - asking which versions should be packaged due to the overwhelming number of releases
  • #214: Direct suggestion for daily releases to reduce notification frequency, which aligns with your structured release cycle proposal

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Nov 11, 2025): This issue might be a duplicate of existing issues. Please check: - #4114: Similar concerns about release frequency from package maintainers (Nix) perspective - asking which versions should be packaged due to the overwhelming number of releases - #214: Direct suggestion for daily releases to reduce notification frequency, which aligns with your structured release cycle proposal Feel free to ignore if none of these address your specific case.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
acp
bad
bug
discussion
docs
documentation
enhancement
extension
good first issue
growth
help-wanted
mcp
model-problem
needs:compliance
nix
opentui
perf
pull-request
Mirrored from GitHub Pull Request
 tui
web
windows
zen
No Label discussion
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#2785
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?