lib/reltool/doc/src/reltool_intro.xml


1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98

<?xml version="1.0" encoding="utf-8" ?>
<!DOCTYPE chapter SYSTEM "chapter.dtd">

<chapter>
  <header>
    <copyright>
      <year>2009</year>
      <year>2013</year>
      <holder>Ericsson AB, All Rights Reserved</holder>
    </copyright>
    <legalnotice>
  The contents of this file are subject to the Erlang Public License,
  Version 1.1, (the "License"); you may not use this file except in
  compliance with the License. You should have received a copy of the
  Erlang Public License along with this software. If not, it can be
  retrieved online at http://www.erlang.org/.

  Software distributed under the License is distributed on an "AS IS"
  basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
  the License for the specific language governing rights and limitations
  under the License.

  The Initial Developer of the Original Code is Ericsson AB.
    </legalnotice>

    <title>Introduction</title>
    <prepared>H&aring;kan Mattsson</prepared>
    <responsible>H&aring;kan Mattsson</responsible>
    <docno></docno>
    <approved>H&aring;kan Mattsson</approved>
    <checked></checked>
    <date></date>
    <rev>%VSN%</rev>
    <file>reltool_intro.xml</file>
  </header>
  <p><c>Reltool</c> is a release management tool. It analyses a given
  Erlang/OTP installation and determines various dependencies between
  applications. The <c>graphical</c> frontend depicts the dependencies and
  enables interactive customization of a target system. The backend provides a
  <c>batch</c> interface for generation of customized target systems.</p>

  <section>
    <title>Scope and Purpose</title>
    <p>This manual describes the Reltool application, as a component of the
    Erlang/Open Telecom Platform development environment. It is assumed that
    the reader is familiar with the Erlang Development Environment, which is
    described in a separate User's Guide.</p>
  </section>

  <section>
    <title>Prerequisites</title>
    <p>The following prerequisites is required for understanding the material
    in the Reltool User's Guide:</p>
    <list type="bulleted">
      <item>
        <p>familiarity with Erlang/OTP system principles and Erlang/OTP design
        principles</p>
      </item>
    </list>
    <p>The application requires Erlang/OTP release R13B02 or later.</p>
  </section>

  <section>
    <title>About This Manual</title>
    <p>In addition to this introductory chapter, the Reltool User's Guide
    contains the following chapters:</p>
    <list type="bulleted">
      <item>
        <p>Chapter 2: "Usage" describes the architecture
          and typical usage of the application.</p>
      </item>
      <item>
        <p>Chapter 3: "Examples" gives some usage examples</p>
      </item>
    </list>
  </section>

  <section>
    <title>Where to Find More Information</title>
    <p>Refer to the following documentation for more information about Reltool
    and about the Erlang/OTP development system:</p>
    <list type="bulleted">
      <item>
        <p>the Reference Manual of <c>Reltool</c></p>
      </item>
      <item>
        <p>the Erlang/OTP <c>System Principles</c></p>
      </item>
      <item>
        <p>the Erlang/OTP <c>Design Principles</c></p>
      </item>
      <item>
        <p>Programming Erlang: Software for a Concurrent World (2007),
        Pragmatic Bookshelf, ISBN13: 9781934356005.</p>
      </item>
    </list>
  </section>
</chapter>