10000 Arduino/package at devyte-eboot · arduino-collections/Arduino · GitHub
[go: up one dir, main page]

Skip to content
{"payload":{"allShortcutsEnabled":false,"path":"package","repo":{"id":370023497,"defaultBranch":"master","name":"Arduino","ownerLogin":"arduino-collections","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2021-05-23T10:33:59.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/84664126?v=4","public":true,"private":false,"isOrgOwned":true},"currentUser":null,"refInfo":{"name":"devyte-eboot","listCacheKey":"v0:1621766046.716144","canEdit":false,"refType":"branch","currentOid":"e8511a053a38013f7dfe1dbee0d2efe0164a6a37"},"tree":{"items":[{"name":"README.md","path":"package/README.md","contentType":"file"},{"name":"build_boards_manager_package.sh","path":"package/build_boards_manager_package.sh","contentType":"file"},{"name":"deploy_package_index.sh","path":"package/deploy_package_index.sh","contentType":"file"},{"name":"drop_versions.py","path":"package/drop_versions.py","contentType":"file"},{"name":"esp8266-arduino-doc.bash","path":"package/esp8266-arduino-doc.bash","contentType":"file"},{"name":"esp8266_github_io_deploy.enc","path":"package/esp8266_github_io_deploy.enc","contentType":"file"},{"name":"merge_packages.py","path":"package/merge_packages.py","contentType":"file"},{"name":"package_esp8266com_index.template.json","path":"package/package_esp8266com_index.template.json","contentType":"file"},{"name":"upload_release.py","path":"package/upload_release.py","contentType":"file"}],"templateDirectorySuggestionUrl":null,"readme":{"displayName":"README.md","richText":"\u003carticle class=\"markdown-body entry-content container-lg\" itemprop=\"text\"\u003e\u003cdiv class=\"markdown-heading\" dir=\"auto\"\u003e\u003ch1 tabindex=\"-1\" class=\"heading-element\" dir=\"auto\"\u003eRelease tools\u003c/h1\u003e\u003ca id=\"user-content-release-tools\" class=\"anchor\" aria-label=\"Permalink: Release tools\" href=\"#release-tools\"\u003e\u003csvg class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"\u003e\u003cpath d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"\u003e\u003c/path\u003e\u003c/svg\u003e\u003c/a\u003e\u003c/div\u003e\n\u003cdiv class=\"markdown-heading\" dir=\"auto\"\u003e\u003ch2 tabindex=\"-1\" class=\"heading-element\" dir=\"auto\"\u003eRelease model\u003c/h2\u003e\u003ca id=\"user-content-release-model\" class=\"anchor\" aria-label=\"Permalink: Release model\" href=\"#release-model\"\u003e\u003csvg class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"\u003e\u003cpath d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"\u003e\u003c/path\u003e\u003c/svg\u003e\u003c/a\u003e\u003c/div\u003e\n\u003cp dir=\"auto\"\u003eThe release model is linear. That means that there is only one main code branch, and releases are snapshots of that branch at specific points in the sequence of commits.\nThe advantage of this model is that the maintenance effort is greatly reduced compared to other release models, such as a branched model.\nThe disadvantage is that progress is ever only forward, and fixes can't be backported to prior releases. this means there is no such thing as a \"stable\" release (however, see Sub releases below).\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eThere are 4 types of releases:\u003c/p\u003e\n\u003cp dir=\"auto\"\u003e\u003cem\u003eMajor releases\u003c/em\u003e\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eThese contain breaking changes, such as big API changes, both in function signature and data representation. When this happens, user apps will require changes to continue to work, and those changes could be significant.\nMajor releases happen seldom, e.g.: every few years.\nIn addition, a Major can contain changes from Minor releases.\u003c/p\u003e\n\u003cp dir=\"auto\"\u003e\u003cem\u003eMinor releases\u003c/em\u003e\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eThese contain new features and bug fixes. Breaking changes should not be included here. The one exception is breaking changes for a feature that is too broken and is not worth fixing, especially if that feature is causing maintenance overhead.\nMinor releases happen maybe 1-3 times per year.\nIn addition, a Minor release can contain changes from Sub releases.\u003c/p\u003e\n\u003cp dir=\"auto\"\u003e\u003cem\u003eSub releases\u003c/em\u003e\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eSub releases are mostly meant for stabilization purposes. Once a Major or Minor release is out, it is possible that critical bugs or issues are found. Given that fixes can't be backported, a sub release is made that includes such critical bug fixes.\nSub releases happen a few weeks after a Major or Minor release.\u003c/p\u003e\n\u003cp dir=\"auto\"\u003e\u003cem\u003eBeta releases\u003c/em\u003e\u003c/p\u003e\n\u003cp dir=\"auto\"\u003eDepending on the number of changes that have been merged since the last release, and on how big and disruptive those changes are, a beta release could be done prior to a Major or Minor. Beta releases are meant to provide an outlook of what the upcoming release will look like, in order to allow users to do early testing and provide feedback. This helps in identifying big issues early on, thereby allowing time to fix them before the final Major or Minor release.\nBeta releases should not be done for Sub releases.\u003c/p\u003e\n\u003cdiv class=\"markdown-heading\" dir=\"auto\"\u003e\u003ch2 tabindex=\"-1\" class=\"heading-element\" dir=\"auto\"\u003eOverview\u003c/h2\u003e\u003ca id=\"user-content-overview\" class=\"anchor\" aria-label=\"Permalink: Overview\" href=\"#overview\"\u003e\u003csvg class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"\u003e\u003cpath d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"\u003e\u003c/path\u003e\u003c/svg\u003e\u003c/a\u003e\u003c/div\u003e\n\u003cp dir=\"auto\"\u003eThis directory contains scripts used to automate the release process of esp8266/Arduino project.\nThe purpose of the release process is to generate the following outputs from the repository:\u003c/p\u003e\n\u003cul dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eBoards manager package index for Arduino IDE (i.e. \u003ccode\u003epackage_esp8266_index.json\u003c/code\u003e). See \u003ca href=\"https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.6.x-package_index.json-format-specification\"\u003especification\u003c/a\u003e of package index file for more info.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eBoards manager package for Arduino IDE. This is a .zip file which contains source code of esp8266/Arduino project, platform.txt, boards.txt and a few other supporting files. See \u003ca href=\"https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5-3rd-party-Hardware-specification\"\u003e3-rd party hardware specification\u003c/a\u003e for more info about the layout of the boards manager package.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eGithub Release for esp8266/Arduino project. This is used to host the boards manager package mentioned above, and also contains the release notes.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cp dir=\"auto\"\u003eHere is a rough overview of the effective release process. See the section below for detailed instructions.\u003c/p\u003e\n\u003col dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eRelease process effectively starts when a maintainer pushes a tag into the repository.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eTravis CI runs a build for this tag, and one of the jobs (with \u003ccode\u003eBUILD_TYPE=package\u003c/code\u003e) is used to prepare the boards manager package. This job runs \u003ccode\u003ebuild_boards_manager_package.sh\u003c/code\u003e.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003e\u003ccode\u003ebuild_boards_manager_package.sh\u003c/code\u003e does a few things to build the boards manager package (.zip) file and the json index:\u003c/p\u003e\n\u003cul dir=\"auto\"\u003e\n\u003cli\u003ePack source files into a zip file, excluding some files and tweaking platform.txt.\u003c/li\u003e\n\u003cli\u003eDownload current latest package index json file from Github Releases. This file contains descriptions of all previous releases.\u003c/li\u003e\n\u003cli\u003eGenerate package index for the new release.\u003c/li\u003e\n\u003cli\u003eCombines new release with previous releases in one json file (using \u003ccode\u003emerge_packages.py\u003c/code\u003e script).\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eTravis CI uploads boards manager package (.zip file) and package index (.json file) to Github Releases, creating a draft release at the same time.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eTravis CI also uploads package index .json file to \u003ccode\u003ehttps://arduino.esp8266.com/stable/package_esp8266_index.json\u003c/code\u003e, i.e. well-known URL used by most users.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eWhen the draft release is created, maintainer edits release description and inserts changelog into the description field, unmarks the release as draft, and publishes the release.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eHousekeeping is performed in Github issue tracker to close the completed milestone, update issue tags, etc.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ol\u003e\n\u003cdiv class=\"markdown-heading\" dir=\"auto\"\u003e\u003ch2 tabindex=\"-1\" class=\"heading-element\" dir=\"auto\"\u003eCreating a release (for maintainers)\u003c/h2\u003e\u003ca id=\"user-content-creating-a-release-for-maintainers\" class=\"anchor\" aria-label=\"Permalink: Creating a release (for maintainers)\" href=\"#creating-a-release-for-maintainers\"\u003e\u003csvg class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"\u003e\u003cpath d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"\u003e\u003c/path\u003e\u003c/svg\u003e\u003c/a\u003e\u003c/div\u003e\n\u003col dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003e\u003ca href=\"https://github.com/esp8266/Arduino/issues/new/choose\"\u003eOpen a new issue\u003c/a\u003e to track activities, which will be closed after the release is done. Copy the checklist below into it, and check the steps one by one as they get completed.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eMake sure that no issues or PRs are assigned to the milestone to be released. If there are any Issues/PRs assigned to the relevant milestone, they should either be addressed, pushed back to a future milestone, or closed.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eAssemble release notes.\u003c/p\u003e\n\u003cul dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eSince most changes are integrated into master using squash-rebase policy (i.e. one commit per PR), \u003ccode\u003egit log --oneline\u003c/code\u003e gives a good overview of changes in the release.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003ePrepare release notes in Markdown format.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eFor changes that are breaking, duplicate those changes and put the duplicate lines into a separate group called Breaking Changes. That group should go at the top of the Changelog. The original lines for the breaking changes should be marked by appending \"(Breaking change)\" to the line. Example:\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003cdiv class=\"snippet-clipboard-content notranslate position-relative overflow-auto\" data-snippet-clipboard-copy-content=\"Breaking Changes\n================\nAPI xyz changed #1234\n...\n\nLibrary - xyz\n=============\nAPI xyz changed #1234 (Breaking change)\n...\"\u003e\u003cpre class=\"notranslate\"\u003e\u003ccode\u003eBreaking Changes\n================\nAPI xyz changed #1234\n...\n\nLibrary - xyz\n=============\nAPI xyz changed #1234 (Breaking change)\n...\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\n\u003cul dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eCombine related changes into the following categories, in that order, including breaking changes with the appended mark:\u003c/p\u003e\n\u003cul dir=\"auto\"\u003e\n\u003cli\u003eBreaking Changes\u003c/li\u003e\n\u003cli\u003eCore\u003c/li\u003e\n\u003cli\u003e\u003cem\u003eLibraries\u003c/em\u003e — one section per library that received changes. If library only had a single change or a few changes, it is also okay to combine changes to a few such libraries under single \"Other Libraries\" entry.\u003c/li\u003e\n\u003cli\u003eUpstream dependencies\u003c/li\u003e\n\u003cli\u003eDocumentation\u003c/li\u003e\n\u003cli\u003eBoards\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eNot all commit descriptions which come from \u003ccode\u003egit log\u003c/code\u003e will explain changes well. Reword items as necessary, with the goal that a general user of this project should be able to understand what the change is related to. Preserve references to PRs or issues (\u003ccode\u003e#XXXX\u003c/code\u003e).\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eAggregate minor fixes (e.g. typos, small documentation changes) in a few items. Focus on preparing a good overview of the release for the users, rather than mentioning every change.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eWhen done, put release notes into a private \u003ca href=\"https://gist.github.com\"\u003eGist\u003c/a\u003e or \u003ca href=\"https://demo.firepad.io\" rel=\"nofollow\"\u003efirepad\u003c/a\u003e and send the link to other maintainers for review.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ol\u003e\n\u003cp dir=\"auto\"\u003eThe following points assume work in a direct clone of the repository, and not in a personal fork.\u003c/p\u003e\n\u003col start=\"4\" dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eMake a PR with the following, \u003ca href=\"https://travis-ci.org/github/esp8266/Arduino/builds/\" rel=\"nofollow\"\u003ewait for Travis CI\u003c/a\u003e, and merge.\u003c/p\u003e\n\u003cul dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003e\u003ca href=\"https://github.com/esp8266/Arduino/blob/master/platform.txt\"\u003eplatform.txt\u003c/a\u003e and \u003ca href=\"https://github.com/esp8266/Arduino/blob/master/package.json\"\u003epackage.json\u003c/a\u003e: update \u003ccode\u003eversion\u003c/code\u003e to the release E.g. \u003ccode\u003e3.0.0\u003c/code\u003e,\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003e\u003ca href=\"https://github.com/esp8266/Arduino/blob/master/cores/esp8266/TZ.h\"\u003ecores/esp8266/TZ.h\u003c/a\u003e: import the latest database with the following shell command:\u003cbr\u003e\n\u003ccode\u003e$ cd tools; sh TZupdate.sh\u003c/code\u003e.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eWait until the release notes have been checked by other maintainers\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eNavigate to \u003ca href=\"https://travis-ci.org/esp8266/Arduino/settings\" rel=\"nofollow\"\u003eTravis CI options\u003c/a\u003e, enable ´Build pushed branches´ (before tagging in next step)\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eTag the latest commit on the master branch. In this project, tags have form \u003ccode\u003eX.Y.Z\u003c/code\u003e, e.g. \u003ccode\u003e3.0.0\u003c/code\u003e, or \u003ccode\u003eX.Y.Z-betaN\u003c/code\u003e for release candidate versions. Notice that there's no \u003ccode\u003ev\u003c/code\u003eat the beginning of the tag. Tags must be annotated, not lightweight tags. To create a tag, use git command (assuming that the master branch is checked out):\u003c/p\u003e\n\u003cdiv class=\"snippet-clipboard-content notranslate position-relative overflow-auto\" data-snippet-clipboard-copy-content=\"git tag -a -m \u0026quot;Release 3.0.0\u0026quot; 3.0.0\"\u003e\u003cpre class=\"notranslate\"\u003e\u003ccode\u003egit tag -a -m \"Release 3.0.0\" 3.0.0\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\n\u003cp dir=\"auto\"\u003enavigate to \u003ca href=\"https://travis-ci.org/esp8266/Arduino/settings\" rel=\"nofollow\"\u003eTravis CI options\u003c/a\u003e, enable \u003ccode\u003eBuild pushed branches\u003c/code\u003e,\u003c/p\u003e\n\u003cp dir=\"auto\"\u003ethen push the tag created above to esp8266/Arduino Github repository:\u003c/p\u003e\n\u003cdiv class=\"snippet-clipboard-content notranslate position-relative overflow-auto\" data-snippet-clipboard-copy-content=\"git push origin 3.0.0\"\u003e\u003cpre class=\"notranslate\"\u003e\u003ccode\u003egit push origin 3.0.0\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\n\u003cp dir=\"auto\"\u003eIn case something goes wrong, release can be canceled at any time:\u003c/p\u003e\n\u003cul dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eTag must be removed (\u003ccode\u003egit tag -d X.Y.Z; git push --delete origin X.Y.Z\u003c/code\u003e)\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eRelease must be deleted: github \u0026gt; releases \u0026gt; edit x.y.z \u0026gt; remove all files \u0026gt; delete button appears\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eWait for Travis CI build for the tag to pass, see \u003ca href=\"https://travis-ci.org/esp8266/Arduino/builds\" rel=\"nofollow\"\u003ehttps://travis-ci.org/esp8266/Arduino/builds\u003c/a\u003e,\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eCheck that the new (draft) release has been created (no editing at this point!), see \u003ca href=\"https://github.com/esp8266/Arduino/releases\"\u003ehttps://github.com/esp8266/Arduino/releases\u003c/a\u003e.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eCheck that the boards manager package .zip file has been successfully uploaded as a release artifact.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eCheck that the package index downloaded from \u003ca href=\"https://arduino.esp8266.com/stable/package_esp8266com_index.json\" rel=\"nofollow\"\u003ehttps://arduino.esp8266.com/stable/package_esp8266com_index.json\u003c/a\u003e contains an entry for the new version (it may not be the first one).\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eReturn to the \u003ca href=\"https://travis-ci.org/esp8266/Arduino/settings\" rel=\"nofollow\"\u003eTravis CI options\u003c/a\u003e and disable \u003ccode\u003eBuild pushed branches\u003c/code\u003e.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eNavigate to release list in Github here \u003ca href=\"https://github.com/esp8266/Arduino/releases\"\u003ehttps://github.com/esp8266/Arduino/releases\u003c/a\u003e, press \"Edit\" button to edit release description, paste release notes, and publish it.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eIn the issue tracker, remove \"staged-for-release\" label for all issues which have it, and close them. Close the milestone associated with the released version (the milestone should be empty per point 2 above)\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eCheck that \u003ca href=\"https://arduino-esp8266.readthedocs.io/en/latest/\" rel=\"nofollow\"\u003ehttps://arduino-esp8266.readthedocs.io/en/latest/\u003c/a\u003e has a new doc build for the new tag, and that \"stable\" points to that build. If a new build did not trigger, log into readthedoc's home here \u003ca href=\"https://readthedocs.org/\" rel=\"nofollow\"\u003ehttps://readthedocs.org/\u003c/a\u003e (account must have been added to project as maintainer) and trigger it manually.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eCreate a commit to the master branch, updating:\u003c/p\u003e\n\u003cul dir=\"auto\"\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eThe version in platform.txt and package.json files. This should correspond to the version of the \u003cem\u003enext\u003c/em\u003e milestone, plus \u003ccode\u003e-dev\u003c/code\u003e suffix. E.g. \u003ccode\u003e3.1.0-dev\u003c/code\u003e.\u003c/p\u003e\n\u003c/li\u003e\n\u003cli\u003e\n\u003cp dir=\"auto\"\u003eIn main README.md go to \"Latest release\" section, change version number in the readthedocs link to the version which was just released, and verify that all links work.\u003c/p\u003e\n\u003c/li\u003e\n\u003c/ul\u003e\n\u003c/li\u003e\n\u003c/ol\u003e\n\u003cdiv class=\"markdown-heading\" dir=\"auto\"\u003e\u003ch2 tabindex=\"-1\" class=\"heading-element\" dir=\"auto\"\u003eChecklist helper, copy-paste into Release Process issue\u003c/h2\u003e\u003ca id=\"user-content-checklist-helper-copy-paste-into-release-process-issue\" class=\"anchor\" aria-label=\"Permalink: Checklist helper, copy-paste into Release Process issue\" href=\"#checklist-helper-copy-paste-into-release-process-issue\"\u003e\u003csvg class=\"octicon octicon-link\" viewBox=\"0 0 16 16\" version=\"1.1\" width=\"16\" height=\"16\" aria-hidden=\"true\"\u003e\u003cpath d=\"m7.775 3.275 1.25-1.25a3.5 3.5 0 1 1 4.95 4.95l-2.5 2.5a3.5 3.5 0 0 1-4.95 0 .751.751 0 0 1 .018-1.042.751.751 0 0 1 1.042-.018 1.998 1.998 0 0 0 2.83 0l2.5-2.5a2.002 2.002 0 0 0-2.83-2.83l-1.25 1.25a.751.751 0 0 1-1.042-.018.751.751 0 0 1-.018-1.042Zm-4.69 9.64a1.998 1.998 0 0 0 2.83 0l1.25-1.25a.751.751 0 0 1 1.042.018.751.751 0 0 1 .018 1.042l-1.25 1.25a3.5 3.5 0 1 1-4.95-4.95l2.5-2.5a3.5 3.5 0 0 1 4.95 0 .751.751 0 0 1-.018 1.042.751.751 0 0 1-1.042.018 1.998 1.998 0 0 0-2.83 0l-2.5 2.5a1.998 1.998 0 0 0 0 2.83Z\"\u003e\u003c/path\u003e\u003c/svg\u003e\u003c/a\u003e\u003c/div\u003e\n\u003cdiv class=\"snippet-clipboard-content notranslate position-relative overflow-auto\" data-snippet-clipboard-copy-content=\"--------------COPY BELOW THIS LINE--------------\n[Reference](https://github.com/esp8266/Arduino/tree/master/package#creating-a-release-for-maintainers) for details.\n\n- [ ] 1. Open a new issue to track activities. \n\n- [ ] 2. Make sure that no issues or PRs are assigned to the milestone to be released.\n\n- [ ] 3. Assemble release notes.\n\n- [ ] 4. Make a PR with the following, [wait for Travis CI](https://travis-ci.org/github/esp8266/Arduino/builds/), and merge.\n\n * [platform.txt](https://github.com/esp8266/Arduino/blob/master/platform.txt)\n * [package.json](https://github.com/esp8266/Arduino/blob/master/package.json)\n * [cores/esp8266/TZ.h](https://github.com/esp8266/Arduino/blob/master/cores/esp8266/TZ.h)\n\n- [ ] 5. Wait until the release notes have been checked by other maintainers\n\n- [ ] 6. Navigate to [Travis CI options](https://travis-ci.org/esp8266/Arduino/settings), enable ´Build pushed branches´ (before tagging in next step)\n\n- [ ] 7. Tag the latest commit on the master branch, then push it to esp8266/Arduino\n\n- [ ] 8. Wait for Travis CI build for the tag to pass, see https://travis-ci.org/esp8266/Arduino/builds,\n\n- [ ] 9. Check that the new (draft) release has been created (no editing at this point!), see https://github.com/esp8266/Arduino/releases. \n\n- [ ] 10. Check that the boards manager package .zip file has been successfully uploaded as a release artifact.\n\n- [ ] 11. Check that the package index downloaded from https://arduino.esp8266.com/stable/package_esp8266com_index.json contains an entry for the new version (it may not be the first one).\n\n- [ ] 12. Return to the [Travis CI options](https://travis-ci.org/esp8266/Arduino/settings) and disable `Build pushed branches`.\n\n- [ ] 13. Navigate to [release list in Github](https://github.com/esp8266/Arduino/releases), press \u0026quot;Edit\u0026quot; button to edit release description, paste release notes, and publish it.\n\n- [ ] 14. In the issue tracker, remove \u0026quot;staged-for-release\u0026quot; label for all issues which have it, and close them. Close the milestone associated with the released version (the milestone should be empty per point 2 above)\n\n- [ ] 15. Check that https://arduino-esp8266.readthedocs.io/en/latest/ has a new doc build for the new tag, and that \u0026quot;stable\u0026quot; points to that build. If a new build did not trigger, log into readthedoc's home here https://readthedocs.org/ (account must have been added to project as maintainer) and trigger it manually.\n\n- [ ] 16. Create a commit to the master branch, updating:\n\n * The version in platform.txt and package.json files. This should correspond to the version of the *next* milestone, plus `-dev` suffix. E.g. `3.1.0-dev`.\n * In main README.md go to \u0026quot;Latest release\u0026quot; section, change version number in the readthedocs link to the version which was just released, and verify that all links work.\n--------------COPY ABOVE THIS LINE--------------\"\u003e\u003cpre class=\"notranslate\"\u003e\u003ccode\u003e--------------COPY BELOW THIS LINE--------------\n[Reference](https://github.com/esp8266/Arduino/tree/master/package#creating-a-release-for-maintainers) for details.\n\n- [ ] 1. Open a new issue to track activities. \n\n- [ ] 2. Make sure that no issues or PRs are assigned to the milestone to be released.\n\n- [ ] 3. Assemble release notes.\n\n- [ ] 4. Make a PR with the following, [wait for Travis CI](https://travis-ci.org/github/esp8266/Arduino/builds/), and merge.\n\n * [platform.txt](https://github.com/esp8266/Arduino/blob/master/platform.txt)\n * [package.json](https://github.com/esp8266/Arduino/blob/master/package.json)\n * [cores/esp8266/TZ.h](https://github.com/esp8266/Arduino/blob/master/cores/esp8266/TZ.h)\n\n- [ ] 5. Wait until the release notes have been checked by other maintainers\n\n- [ ] 6. Navigate to [Travis CI options](https://travis-ci.org/esp8266/Arduino/settings), enable ´Build pushed branches´ (before tagging in next step)\n\n- [ ] 7. Tag the latest commit on the master branch, then push it to esp8266/Arduino\n\n- [ ] 8. Wait for Travis CI build for the tag to pass, see https://travis-ci.org/esp8266/Arduino/builds,\n\n- [ ] 9. Check that the new (draft) release has been created (no editing at this point!), see https://github.com/esp8266/Arduino/releases. \n\n- [ ] 10. Check that the boards manager package .zip file has been successfully uploaded as a release artifact.\n\n- [ ] 11. Check that the package index downloaded from https://arduino.esp8266.com/stable/package_esp8266com_index.json contains an entry for the new version (it may not be the first one).\n\n- [ ] 12. Return to the [Travis CI options](https://travis-ci.org/esp8266/Arduino/settings) and disable `Build pushed branches`.\n\n- [ ] 13. Navigate to [release list in Github](https://github.com/esp8266/Arduino/releases), press \"Edit\" button to edit release description, paste release notes, and publish it.\n\n- [ ] 14. In the issue tracker, remove \"staged-for-release\" label for all issues which have it, and close them. Close the milestone associated with the released version (the milestone should be empty per point 2 above)\n\n- [ ] 15. Check that https://arduino-esp8266.readthedocs.io/en/latest/ has a new doc build for the new tag, and that \"stable\" points to that build. If a new build did not trigger, log into readthedoc's home here https://readthedocs.org/ (account must have been added to project as maintainer) and trigger it manually.\n\n- [ ] 16. Create a commit to the master branch, updating:\n\n * The version in platform.txt and package.json files. This should correspond to the version of the *next* milestone, plus `-dev` suffix. E.g. `3.1.0-dev`.\n * In main README.md go to \"Latest release\" section, change version number in the readthedocs link to the version which was just released, and verify that all links work.\n--------------COPY ABOVE THIS LINE--------------\n\u003c/code\u003e\u003c/pre\u003e\u003c/div\u003e\n\u003c/article\u003e","errorMessage":null,"headerInfo":{"toc":[{"level":1,"text":"Release tools","anchor":"release-tools","htmlText":"Release tools"},{"level":2,"text":"Release model","anchor":"release-model","htmlText":"Release model"},{"level":2,"text":"Overview","anchor":"overview","htmlText":"Overview"},{"level":2,"text":"Creating a release (for maintainers)","anchor":"creating-a-release-for-maintainers","htmlText":"Creating a release (for maintainers)"},{"level":2,"text":"Checklist helper, copy-paste into Release Process issue","anchor":"checklist-helper-copy-paste-into-release-process-issue","htmlText":"Checklist helper, copy-paste into Release Process issue"}],"siteNavLoginPath":"/login?return_to=https%3A%2F%2Fgithub.com%2Farduino-collections%2FArduino%2Ftree%2Fdevyte-eboot%2Fpackage"}},"totalCount":9,"showBranchInfobar":true},"fileTree":{"":{"items":[{"name":".github","path":".github","contentType":"directory"},{"name":"bootloaders","path":"bootloaders","contentType":"directory"},{"name":"cores","path":"cores","contentType":"directory"},{"name":"doc","path":"doc","contentType":"directory"},{"name":"libraries","path":"libraries","contentType":"directory"},{"name":"package","path":"package","contentType":"directory"},{"name":"tests","path":"tests","contentType":"directory"},{"name":"tools","path":"tools","contentType":"directory"},{"name":"variants","path":"variants","contentType":"directory"},{"name":".gitignore","path":".gitignore","contentType":"file"},{"name":".gitmodules","path":".gitmodules","contentType":"file"},{"name":".travis.yml","path":".travis.yml","contentType":"file"},{"name":"ISSUE_TEMPLATE.md","path":"ISSUE_TEMPLATE.md","contentType":"file"},{"name":"LICENSE","path":"LICENSE","contentType":"file"},{"name":"POLICY.md","path":"POLICY.md","contentType":"file"},{"name":"README.md","path":"README.md","contentType":"file"},{"name":"boards.txt","path":"boards.txt","contentType":"file"},{"name":"keywords.txt","path":"keywords.txt","contentType":"file"},{"name":"package.json","path":"package.json","contentType":"file"},{"name":"platform.txt","path":"platform.txt","contentType":"file"},{"name":"programmers.txt","path":"programmers.txt","contentType":"file"}],"totalCount":21}},"fileTreeProcessingTime":7.012414,"foldersToFetch":[],"treeExpanded":true,"symbolsExpanded":false,"csrf_tokens":{"/arduino-collections/Arduino/branches":{"post":"dhLMfAoztAHrA_nuMPFsyR0H82VvLQYeDD4utB-IkWoqzpr683fDkYrkn86VmHRfAibDmdkhAiPqWaLx4uAuKA"},"/arduino-collections/Arduino/branches/fetch_and_merge/devyte-eboot":{"post":"OnY2h1l-5dpNYRV5tyiDctUCADe4QH8IgOyXLBZdnmxOyIqA8-gUmcZI4JB2HxuVpOSHEc3iKXIOdKH98FuTzw"},"/arduino-collections/Arduino/branches/fetch_and_merge/devyte-eboot?discard_changes=true":{"post":"jH29lm6AI71Pfoj5EOVJO5bsugZSfylO7qNrilIgdhf4wwGRxBbS_sRXfRDR0tHc5wo9ICfdfzRgO11btCZ7tA"}}},"title":"Arduino/package at devyte-eboot · arduino-collections/Arduino","appPayload":{"helpUrl":"https://docs.github.com","findFileWorkerPath":"/assets-cdn/worker/find-file-worker-263cab1760dd.js","findInFileWorkerPath":"/assets-cdn/worker/find-in-file-worker-1b17b3e7786a.js","githubDevUrl":null,"enabled_features":{"code_nav_ui_events":false,"react_blob_overlay":false,"accessible_code_button":true}}}
0