@ciao-lang/ts-ciao-interface

Version:

Simple Ciao interface for node.

4 lines • 3.58 kB

HTML

<!DOCTYPE HTML><html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"/><meta name="viewport" content="width=device-width, initial-scale=1"/><meta name="theme-color" content="#273f79"/><link rel="stylesheet" href="lpdoc.css" type="text/css"/><script type="text/javascript" src="lpdoc.js"></script><title>Producing new releases — </title></head><body><div class="lpdoc-page fixleftbar"><a href="#" id="sidebar-toggle-button" class="lpdoc-navbutton"><span id="sidebar-button-arrow">☰</span></a><div id="sidebar" class="lpdoc-sidebar"><div style="height: 40px; margin-left: auto; margin-right: auto"><img src="ciao-grimoire-128h_autofig.png" width=auto height=100%></div><div class="lpdoc-nav"><span class="lpdoc-on-right"><a class="lpdoc-navbutton" href="CiaoDevel.html">↑</a><a class="lpdoc-navbutton" href="CodeReviews.html">←</a><a class="lpdoc-navbutton" href="CiaoBiblio.html">→</a><a class="lpdoc-navbutton" href="CiaoDevelsearch.html">🔍</a></span><span><a href="CiaoDevelfulltoc.html">TOC</a></span></div><hr></hr><ul class="lpdoc-itemize-sectpath"><li><a href="CiaoDevel.html">CiaoDevel Reference Manual</a> »<br/> </li><li><a href=""><strong>Producing new releases</strong></a></li></ul></div><div class="lpdoc-main"><div id=""><h1>Producing new releases</h1><a class="lpdoc-idx-anchor" href="CiaoDevelsearch.html#NewRelease"></a> <strong>Author(s):</strong> <a class="lpdoc-idx-anchor" id="The Ciao Development Team" href="CiaoDevelsearch.html#The Ciao Development Team">The Ciao Development Team</a>.<p> Depending on the number changes, it may be necessary to raise the version number (see <span class="lpdoc-var">GlobalVersion</span>, <span class="lpdoc-var">GlobalPath</span>, <a class="lpdoc-idx-anchor" id="0" href="CiaoDevelsearch.html#version/1"><tt>version/1</tt></a> at <tt>Manifest.pl</tt>, etc.).<p>Given an odd minor number version of the system (e.g., development <tt>v1.1</tt>), the release plan consists on selecting some new features, test and fix the system as required, compose a changelog, increment the version to an even number (e.g., stable <tt>v1.2</tt>), save this point in the source history, and increment again the version number to an odd number (e.g., development <tt>v1.3</tt>).<p>This is detailed as follows:<p><ul> <li>Identify the new features and important changes for the new release (the changelog). This usually means going through the Git log and grouping all the changes in a way similar to what appears in <tt>core/doc/CHANGELOG.pl</tt> for previous versions. <li>Iterate through: test existing, new, and improved features; check that installation from source (both local and global installs, in all supported platforms) work; check that distributions work; fix bugs if needed, or postpone/drop new features. <li>When in a satisfactory state, add an updated changelog to <tt>core/doc/CHANGELOG.pl</tt> and increment the version number. Commit and push the changes. <li>Tag the commit (omit COMMIT_ID to use HEAD): <pre class="lpdoc-codeblock">git tag -a vMajor.Minor.Patch COMMIT_ID -m <span class="string">'Version jumped to Major.Minor.Patch'</span> git push origin vMajor.Minor.Patch</pre> <li>Make sure that distributions are up-to-date, update the website, brochure, and announce the release to <tt>ciao-users</tt> mailing list. <li>Increment the version number again to an odd number for the new development version. </ul> <br/></div><div class="lpdoc-footer">Generated with LPdoc using Ciao</div></div><div class="lpdoc-clearer"></div></div></body></html>