-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Releasing
xterm.js is released approximately once a month. As the release date approaches say around 3-5 days before the scheduled date the code is frozen, this means all PRs that are non-trivial or important bug fixes are deferred until after the release is done. This helps minimize the risk of bugs coming in at last second that could cause the need for a patch release.
As the date approaches the release notes need to be created. Here are the steps for this:
-
Go to the releases page and create a new draft.
-
Copy the headers from a recent release.
-
Open the pull requests page and make sure that all recent pull requests have correct milestones attached to them as sometimes PRs get merged in without a milestone. While doing this, also check the referenced issues to make sure they are closed off and assigned to the milestone too.
-
Open the pull requests page again and assign the release's milestone.
-
Go through each of the PRs and make a line item under the heading that makes the most sense, use this format:
- (#issue) via @author
-
Go through the release and merge similar issues where it makes sense. Typically do this for internal improvements as they're not as important for end users, or for PRs which were done as a series, for example:
- (#issue1, #issue2) via @author1, @author2
TODO@paris
After publishing the build can be verified easily using the electron example in node-pty. Just clone that, update the dependency and run the project.
Once the release is done (or shortly before to unblock master), branch off release/<major>.<minor> (eg release/3.5) and push to xtermjs/xterm.js. This branch is temporary and should be deleted once no more released are expected for that minor version.