Linux cpanel.rrshost.in 5.15.0-25-generic #25-Ubuntu SMP Wed Mar 30 15:54:22 UTC 2022 x86_64
Apache
: 109.123.238.221 | : 172.69.130.108
128 Domain
8.2.28
aev999
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
HASH IDENTIFIER
README
+ Create Folder
+ Create File
/
usr /
share /
doc /
graphicsmagick /
www /
[ HOME SHELL ]
Name
Size
Permission
Action
images
[ DIR ]
drwxr-xr-x
wand
[ DIR ]
drwxr-xr-x
ChangeLog-2001.html
23.56
KB
-rw-r--r--
ChangeLog-2002.html
95.11
KB
-rw-r--r--
ChangeLog-2003.html
257.78
KB
-rw-r--r--
ChangeLog-2004.html
87.64
KB
-rw-r--r--
ChangeLog-2005.html
58.03
KB
-rw-r--r--
ChangeLog-2006.html
14.43
KB
-rw-r--r--
ChangeLog-2007.html
57.83
KB
-rw-r--r--
ChangeLog-2008.html
127.75
KB
-rw-r--r--
ChangeLog-2009.html
106.29
KB
-rw-r--r--
ChangeLog-2010.html
44.81
KB
-rw-r--r--
ChangeLog-2011.html
40.59
KB
-rw-r--r--
ChangeLog-2012.html
58.38
KB
-rw-r--r--
ChangeLog-2013.html
35.93
KB
-rw-r--r--
ChangeLog-2014.html
57.66
KB
-rw-r--r--
ChangeLog-2015.html
111.57
KB
-rw-r--r--
ChangeLog-2016.html
59.17
KB
-rw-r--r--
ChangeLog-2017.html
72.3
KB
-rw-r--r--
ChangeLog-2018.html
170.85
KB
-rw-r--r--
ChangeLog-2019.html
84.87
KB
-rw-r--r--
ChangeLog-2020.html
74.61
KB
-rw-r--r--
ChangeLog-2021.html
50.82
KB
-rw-r--r--
Changes.html
4.78
KB
-rw-r--r--
Copyright.html
15.27
KB
-rw-r--r--
FAQ.html
47.41
KB
-rw-r--r--
GraphicsMagick.html
376.79
KB
-rw-r--r--
Hg.html
15.76
KB
-rw-r--r--
INSTALL-unix.html
60.78
KB
-rw-r--r--
INSTALL-windows.html
40.33
KB
-rw-r--r--
ImageMagickObject.html
7.17
KB
-rw-r--r--
NEWS.html
211.05
KB
-rw-r--r--
OpenMP.html
12.77
KB
-rw-r--r--
README.html
22.68
KB
-rw-r--r--
animate.html
41.85
KB
-rw-r--r--
authors.html
8.6
KB
-rw-r--r--
batch.html
10.6
KB
-rw-r--r--
benchmark.html
11.78
KB
-rw-r--r--
benchmarks.html
7.1
KB
-rw-r--r--
bugs.html
2.89
KB
-rw-r--r--
color.html
30.19
KB
-rw-r--r--
compare.html
19.27
KB
-rw-r--r--
composite.html
39.9
KB
-rw-r--r--
configure-target-setup.png
7.21
KB
-rw-r--r--
conjure.html
15.4
KB
-rw-r--r--
contribute.html
6.85
KB
-rw-r--r--
convert.html
90.16
KB
-rw-r--r--
display.html
140.58
KB
-rw-r--r--
docutils-api.css
8.56
KB
-rw-r--r--
docutils-articles.css
9.95
KB
-rw-r--r--
download.html
7.25
KB
-rw-r--r--
favicon.ico
922
B
-rw-r--r--
formats.html
41.29
KB
-rw-r--r--
gm.html
891.41
KB
-rw-r--r--
identify.html
13.4
KB
-rw-r--r--
import.html
30.34
KB
-rw-r--r--
index.html
9.75
KB
-rw-r--r--
links.html
14.44
KB
-rw-r--r--
magick.css
2.36
KB
-rw-r--r--
miff.html
17.44
KB
-rw-r--r--
mission.html
3.32
KB
-rw-r--r--
mogrify.html
81.71
KB
-rw-r--r--
montage.html
54.05
KB
-rw-r--r--
motion-picture.html
32.02
KB
-rw-r--r--
perl.html
54.33
KB
-rw-r--r--
process.html
5.97
KB
-rw-r--r--
programming.html
5.74
KB
-rw-r--r--
project.html
3.82
KB
-rw-r--r--
quantize.html
11.81
KB
-rw-r--r--
reference.html
2.42
KB
-rw-r--r--
security.html
19.6
KB
-rw-r--r--
smile.c.gz
982
B
-rw-r--r--
thanks.html
6.07
KB
-rw-r--r--
time.html
4.77
KB
-rw-r--r--
tools.html
11.6
KB
-rw-r--r--
utilities.html
4.99
KB
-rw-r--r--
version.html
5.98
KB
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : process.html
<?xml version="1.0" encoding="utf-8" ?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> <meta name="generator" content="Docutils 0.16: http://docutils.sourceforge.net/" /> <title>GraphicsMagick Development Process</title> <link rel="stylesheet" href="docutils-articles.css" type="text/css" /> </head> <body> <div class="banner"> <img src="images/gm-107x76.png" alt="GraphicMagick logo" width="107" height="76" /> <span class="title">GraphicsMagick</span> <form action="http://www.google.com/search"> <input type="hidden" name="domains" value="www.graphicsmagick.org" /> <input type="hidden" name="sitesearch" value="www.graphicsmagick.org" /> <span class="nowrap"><input type="text" name="q" size="25" maxlength="255" /> <input type="submit" name="sa" value="Search" /></span> </form> </div> <div class="navmenu"> <ul> <li><a href="index.html">Home</a></li> <li><a href="project.html">Project</a></li> <li><a href="download.html">Download</a></li> <li><a href="README.html">Install</a></li> <li><a href="Hg.html">Source</a></li> <li><a href="NEWS.html">News</a> </li> <li><a href="utilities.html">Utilities</a></li> <li><a href="programming.html">Programming</a></li> <li><a href="reference.html">Reference</a></li> </ul> </div> <div class="document" id="graphicsmagick-development-process"> <h1 class="title">GraphicsMagick Development Process</h1> <!-- -*- mode: rst -*- --> <!-- This text is in reStucturedText format, so it may look a bit odd. --> <!-- See http://docutils.sourceforge.net/rst.html for details. --> <p>In order to ensure an orderly development process, and assure the highest quality releases, a development process has been established for GraphicsMagick.</p> <div class="section" id="phases-of-development"> <h1>Phases of Development</h1> <p>Four major development phases have been identified. These are the feature development phase, snapshot phase, beta phase, and release phase. The phases used depend on the nature of preceding development. The Beta phase is usually skipped. The descriptions of these phases are as follows:</p> <div class="section" id="feature-development-phase"> <h2>Feature Development Phase</h2> <blockquote> <p>The feature development phase is a time of rapid development and innovation. Work is normally done on Mercurial 'tip'. During the feature development phase, Mercurial is the only way to access the work in progress. Before updates are committed to Mercurial, they should be proven to compile on at least one architecture and pass the test suite ('make distcheck').</p> <p>Entry Criteria: There is a plan for feature development.</p> <p>Exit Criteria: Test suite passes on at least one machine.</p> </blockquote> </div> <div class="section" id="snapshot-phase"> <h2>Snapshot Phase</h2> <blockquote> <p>The snapshot phase is entered when it is decided that the work is stable enough for non-developers to test. API and user interfaces should be stable before the snapshot phase begins in order to avoid confusion. Snapshot development is done on Mercurial 'tip'. Snapshot packages are identified by the date of the snapshot, and no Mercurial branching or tagging is performed to support the snapshot.</p> <p>Entry Criteria: Interfaces are stable, and code compiles and runs on multiple architectures.</p> <p>Exit Criteria: Code is release quality. The test suite must show 100% completion for Q:8 and Q:16 quantum depths on at least three operating environments.</p> </blockquote> </div> <div class="section" id="beta-phase"> <h2>Beta Phase</h2> <blockquote> <p>The Beta phase (usually only occuring at the beginning of a major release cycle) is entered when the work is feature complete, the package passes all tests, and it is considered time for versioned releases. As the first step of entering the beta phase, a release branch is created off of the trunk to support change sets for the release. The purpose of the beta phase is to wring out any remaining bugs prior to release. When a beta package is prepared, a release tag is applied to the associated release branch in Mercurial.</p> <p>Entry Criteria: Code is release quality.. The test suite must show 100% completion for Q:8 and Q:16 quantum depths on at least three operating environments.</p> <p>Exit Criteria: The test suite must show 100% completion for Q:8, Q:16, and Q:32 quantum depths on at least three operating environments. The current beta package is determined to be sufficiently flawless for a final release.</p> </blockquote> </div> <div class="section" id="release-phase"> <h2>Release Phase</h2> <blockquote> <p>The release phase is entered when the most recent Beta (or snapshot) is considered to be of acceptable quality for a release or bug-fixes have been prepared based on a previous release. At this time, a formal release tag is applied to the release branch, and release packages are created. Once a release tag has been applied to a release branch, that release branch is considered to be in release state and may only be used to prepare additional releases intended to correct bugs found in preceding releases. The initial release on a release branch has a two-digit (i.e. X.X) release designation. Bug-fix releases have a three-digit (i.e. X.X.X) release designation. A release designation may only be used once. If a problem is discovered with the release package, a new release number is assigned to support the corrected release package.</p> <p>Entry Criteria: The test suite must show 100% completion for Q:8, Q:16, and Q:32 quantum depths on at least three operating environments. The current beta package is determined to be sufficiently flawless for a final release.</p> <p>Exit Criteria: None</p> </blockquote> </div> </div> </div> <hr class="docutils"> <div class="document"> <p><a href="Copyright.html">Copyright</a> © GraphicsMagick Group 2002 - 2022<!--SPONSOR_LOGO--></p> </div> </body> </html>
Close
