github.com/kaydxh/golang@v0.0.131/pkg/gocv/cgo/third_path/graphics-magick/share/doc/GraphicsMagick/www/process.html (about)

     1  <?xml version="1.0" encoding="utf-8" ?>
     2  <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
     3  <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
     4  <head>
     5  <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
     6  <meta name="generator" content="Docutils 0.15.2: http://docutils.sourceforge.net/" />
     7  <title>GraphicsMagick Development Process</title>
     8  <link rel="stylesheet" href="docutils-articles.css" type="text/css" />
     9  </head>
    10  <body>
    11  
    12  <div class="banner">
    13  <img src="images/gm-107x76.png" alt="GraphicMagick logo" width="107" height="76" />
    14  <span class="title">GraphicsMagick</span>
    15  <form action="http://www.google.com/search">
    16  	<input type="hidden" name="domains" value="www.graphicsmagick.org" />
    17  	<input type="hidden" name="sitesearch" value="www.graphicsmagick.org" />
    18      <span class="nowrap"><input type="text" name="q" size="25" maxlength="255" />&nbsp;<input type="submit" name="sa" value="Search" /></span>
    19  </form>
    20  </div>
    21  
    22  <div class="navmenu">
    23  <ul>
    24  <li><a href="index.html">Home</a></li>
    25  <li><a href="project.html">Project</a></li>
    26  <li><a href="download.html">Download</a></li>
    27  <li><a href="README.html">Install</a></li>
    28  <li><a href="Hg.html">Source</a></li>
    29  <li><a href="NEWS.html">News</a> </li>
    30  <li><a href="utilities.html">Utilities</a></li>
    31  <li><a href="programming.html">Programming</a></li>
    32  <li><a href="reference.html">Reference</a></li>
    33  </ul>
    34  </div>
    35  <div class="document" id="graphicsmagick-development-process">
    36  <h1 class="title">GraphicsMagick Development Process</h1>
    37  
    38  <!-- -*- mode: rst -*- -->
    39  <!-- This text is in reStucturedText format, so it may look a bit odd. -->
    40  <!-- See http://docutils.sourceforge.net/rst.html for details. -->
    41  <p>In order to ensure an orderly development process, and assure the highest
    42  quality releases, a development process has been established for
    43  GraphicsMagick.</p>
    44  <div class="section" id="phases-of-development">
    45  <h1>Phases of Development</h1>
    46  <p>Four major development phases have been identified. These are the
    47  feature development phase, snapshot phase, beta phase, and release
    48  phase.  The phases used depend on the nature of preceding development.
    49  The Beta phase is usually skipped. The descriptions of these phases
    50  are as follows:</p>
    51  <div class="section" id="feature-development-phase">
    52  <h2>Feature Development Phase</h2>
    53  <blockquote>
    54  <p>The feature development phase is a time of rapid development and
    55  innovation. Work is normally done on Mercurial 'tip'.  During the
    56  feature development phase, Mercurial is the only way to access the
    57  work in progress. Before updates are committed to Mercurial, they
    58  should be proven to compile on at least one architecture and pass
    59  the test suite ('make distcheck').</p>
    60  <p>Entry Criteria: There is a plan for feature development.</p>
    61  <p>Exit Criteria: Test suite passes on at least one machine.</p>
    62  </blockquote>
    63  </div>
    64  <div class="section" id="snapshot-phase">
    65  <h2>Snapshot Phase</h2>
    66  <blockquote>
    67  <p>The snapshot phase is entered when it is decided that the work is
    68  stable enough for non-developers to test. API and user interfaces
    69  should be stable before the snapshot phase begins in order to avoid
    70  confusion. Snapshot development is done on Mercurial 'tip'. Snapshot
    71  packages are identified by the date of the snapshot, and no Mercurial
    72  branching or tagging is performed to support the snapshot.</p>
    73  <p>Entry Criteria: Interfaces are stable, and code compiles and runs on
    74  multiple architectures.</p>
    75  <p>Exit Criteria: Code is release quality. The test suite must show
    76  100% completion for Q:8 and Q:16 quantum depths on at least three
    77  operating environments.</p>
    78  </blockquote>
    79  </div>
    80  <div class="section" id="beta-phase">
    81  <h2>Beta Phase</h2>
    82  <blockquote>
    83  <p>The Beta phase (usually only occuring at the beginning of a major
    84  release cycle) is entered when the work is feature complete, the
    85  package passes all tests, and it is considered time for versioned
    86  releases. As the first step of entering the beta phase, a release
    87  branch is created off of the trunk to support change sets for the
    88  release. The purpose of the beta phase is to wring out any remaining
    89  bugs prior to release. When a beta package is prepared, a release
    90  tag is applied to the associated release branch in Mercurial.</p>
    91  <p>Entry Criteria: Code is release quality.. The test suite must show
    92  100% completion for Q:8 and Q:16 quantum depths on at least three
    93  operating environments.</p>
    94  <p>Exit Criteria: The test suite must show 100% completion for Q:8, Q:16,
    95  and Q:32 quantum depths on at least three operating environments. The
    96  current beta package is determined to be sufficiently flawless for a
    97  final release.</p>
    98  </blockquote>
    99  </div>
   100  <div class="section" id="release-phase">
   101  <h2>Release Phase</h2>
   102  <blockquote>
   103  <p>The release phase is entered when the most recent Beta (or snapshot)
   104  is considered to be of acceptable quality for a release or bug-fixes
   105  have been prepared based on a previous release. At this time, a
   106  formal release tag is applied to the release branch, and release
   107  packages are created. Once a release tag has been applied to a
   108  release branch, that release branch is considered to be in release
   109  state and may only be used to prepare additional releases intended
   110  to correct bugs found in preceding releases. The initial release on
   111  a release branch has a two-digit (i.e.  X.X) release
   112  designation. Bug-fix releases have a three-digit (i.e.  X.X.X)
   113  release designation. A release designation may only be used once. If
   114  a problem is discovered with the release package, a new release
   115  number is assigned to support the corrected release package.</p>
   116  <p>Entry Criteria: The test suite must show 100% completion for Q:8, Q:16,
   117  and Q:32 quantum depths on at least three operating environments. The
   118  current beta package is determined to be sufficiently flawless for a
   119  final release.</p>
   120  <p>Exit Criteria: None</p>
   121  </blockquote>
   122  <hr class="docutils" />
   123  <p>Copyright © GraphicsMagick Group 2002 - 2020</p>
   124  </div>
   125  </div>
   126  </div>
   127  </body>
   128  </html>