litvinovg/vitro
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

NIHVIVO-3103 Convert 1.3 references to 1.4 references.

Browse source
This commit is contained in:
j2blake 2011-11-16 17:34:17 +00:00
parent 4072046c99
commit 2b312db0e6
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
doc/install.html
View file

@ -3,7 +3,7 @@
<head> <head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8"> <meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta charset="utf-8"> <meta charset="utf-8">
<title>Vitro Version 1.3 Installation Guide</title> <title>Vitro Version 1.4 Installation Guide</title>
<link rel="stylesheet" href="./css/doc.css" media="screen"> <link rel="stylesheet" href="./css/doc.css" media="screen">
</head> </head>
<body> <body>
@ -12,7 +12,7 @@
</div> </div>
<!-- Start of content --> <!-- Start of content -->
<div id="wrapper-content" role="main"> <div id="wrapper-content" role="main">
<h1>Vitro Version 1.3 Installation Guide</h1> <h1>Vitro Version 1.4 Installation Guide</h1>
<small> <small>
November 15, 2011 November 15, 2011
</small> </small>
@ -22,7 +22,7 @@
<a href="#introduction">Introduction to the Vitro installation</a> <a href="#introduction">Introduction to the Vitro installation</a>
</li> </li>
<li> <li>
<a href="#installation">Installation process for Version 1.3</a> <a href="#installation">Installation process for Version 1.4</a>
</li> </li>
</ul> </ul>
</toc> </toc>
@ -154,16 +154,16 @@
<h4>Release schedule and names</h4> <h4>Release schedule and names</h4>
<p> <p>
Currently, the Vitro release schedule is coordinated with the VIVO releases, Currently, the Vitro release schedule is coordinated with the VIVO releases,
so version 1.3 of Vitro forms the basis of version 1.3 of VIVO. so version 1.4 of Vitro forms the basis of version 1.4 of VIVO.
In the Vitro code repository, the release tags illustrate this relationship. In the Vitro code repository, the release tags illustrate this relationship.
For example, the Vitro revision that was tagged for version 1.3 of VIVO is named “rel-vivo-1.3” For example, the Vitro revision that was tagged for version 1.4 of VIVO is named “rel-vivo-1.4”
</p> </p>
<p> <p>
As the project progresses, As the project progresses,
we will also see Vitro releases named for versions of Datastar and other Vitro-based products. we will also see Vitro releases named for versions of Datastar and other Vitro-based products.
</p> </p>
<hr><!-- Page break --><!-- Installation process for Version 1.3 --><h2 id="installation">Installation process for Version 1.3</h2> <hr><!-- Page break --><!-- Installation process for Version 1.4 --><h2 id="installation">Installation process for Version 1.4</h2>
<p> <p>
This document is a summary of the Vitro installation process. This document is a summary of the Vitro installation process.
</p> </p>