starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Daily or Weekly Preview Releases? #11031

New Issue
Closed
opened 2026-01-31 02:36:47 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:36:47 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Oct 15, 2020).

Hello,

I use Terminal Preview, however its release schedule is too slow for a preview IMO.

Can you please consider releasing previews in a daily (like firefox fenix on android) or weekly schedule?

Or, maybe add another Terminal Nightly that has faster releases..

Originally created by @ghost on GitHub (Oct 15, 2020). Hello, I use Terminal Preview, however its release schedule is too slow for a preview IMO. Can you please consider releasing previews in a daily (like firefox fenix on android) or weekly schedule? Or, maybe add another Terminal Nightly that has faster releases..
claunia added the Issue-QuestionResolution-AnsweredResolution-Duplicate labels 2026-01-31 02:36:47 +00:00
claunia commented 2026-01-31 02:36:49 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 15, 2020):

I'm not sure what the benefit of a faster release cadence would be for the Terminal, to be honest. We're not moving that much code on a day-to-day basis that would make a nightly build valuable IMO. I think the team's preference here is that a longer release cadence (monthly instead of weekly) allows for us a little more wiggle room in getting bugs sorted out and features polished before pushing them to the general public. If we were to release weekly, we'd inevitably have to deal with the community reporting known issues that we're planning on fixing, lowering overall satisfaction with the app. For a team of our size, it's just not that feasible IMO.

@zadjii-msft commented on GitHub (Oct 15, 2020): I'm not sure what the benefit of a faster release cadence would be for the Terminal, to be honest. We're not moving _that much_ code on a day-to-day basis that would make a nightly build valuable IMO. I think the team's preference here is that a longer release cadence (monthly instead of weekly) allows for us a little more wiggle room in getting bugs sorted out and features polished before pushing them to the general public. If we were to release weekly, we'd inevitably have to deal with the community reporting known issues that we're planning on fixing, lowering overall satisfaction with the app. For a team of our size, it's just not that feasible IMO.
claunia commented 2026-01-31 02:36:49 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 15, 2020):

Well, my thinking was that the terminal is pretty stable, but has plenty of big and small feature requests, which get implemented every now and then. Also, the major bugs with the terminal are already known and reported. So, a faster release schedule would allow people to use these newly implemented features without waiting a month.
In any case, you are the maintainers of the project, so you should decide whether this is worth it or is it more trouble.

@ghost commented on GitHub (Oct 15, 2020): Well, my thinking was that the terminal is pretty stable, but has plenty of big and small feature requests, which get implemented every now and then. Also, the major bugs with the terminal are already known and reported. So, a faster release schedule would allow people to use these newly implemented features without waiting a month. In any case, you are the maintainers of the project, so you should decide whether this is worth it or is it more trouble.
claunia commented 2026-01-31 02:36:49 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Oct 16, 2020):

/dup #774

I'm not averse to this, we just haven't had engineering time to stand it up and evaluate the cost of throwing it in a storage bucket somewhere 😄

@DHowett commented on GitHub (Oct 16, 2020): /dup #774 I'm not averse to this, we just haven't had engineering time to stand it up and evaluate the cost of throwing it in a storage bucket somewhere :smile:
claunia commented 2026-01-31 02:36:50 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 16, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Oct 16, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Question Resolution-Answered Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#11031
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?