forked from M-Labs/artiq
22 lines
1.1 KiB
ReStructuredText
22 lines
1.1 KiB
ReStructuredText
Release process
|
|
===============
|
|
|
|
Maintain ``RELEASE_NOTES.rst`` with a list of new features and API changes in each major release.
|
|
|
|
Major releases
|
|
--------------
|
|
|
|
1. Create branch release-X from master.
|
|
2. Ensure that release versions of all packages required are available under the ``main`` label in conda. Ensure that new packages in ``main`` do not break older ARTIQ releases.
|
|
3. Remove any unfinished features.
|
|
4. Test and fix any problems found.
|
|
5. If you have willing testers for release candidates, tag X.0rc0, have it build, and point testers there. Iterate over the previous points with new release candidates if necessary.
|
|
6. Tag X.0, have it build, and copy its packages to ``main`` channel.
|
|
|
|
Minor (bugfix) releases
|
|
-----------------------
|
|
|
|
1. Backport bugfixes from the master branch or fix bugs specific to old releases into the currently maintained release-X branch(es).
|
|
2. When significant bugs have been fixed, tag X.Y+1.
|
|
3. To help dealing with regressions, no new features or refactorings should be implemented in release-X branches. Those happen in the master branch, and then a new release-X+1 branch is created.
|