epics/epics-base
0
0
Fork 0
Code Issues Pull Requests Projects Wiki Activity

Update version numbers in documentation for 3.15.3

Browse Source
This commit is contained in:
Andrew Johnson
2015-05-15 10:06:06 -05:00
parent 196baac7da
commit 9946681f72
5 changed files with 43 additions and 48 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
documentation/KnownProblems.html
View File

@ -4,17 +4,17 @@
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>Known Problems in R3.15.2</title>
<title>Known Problems in R3.15.3</title>
</head>
<body>
<h1 style="text-align: center">EPICS Base R3.15.2: Known Problems</h1>
<h1 style="text-align: center">EPICS Base R3.15.3: Known Problems</h1>
<p>Any patch files linked below should be applied at the root of the
base-3.15.2 tree. Download them, then use the GNU Patch program as
base-3.15.3 tree. Download them, then use the GNU Patch program as
follows:</p>
<blockquote><pre>% <b>cd <i>/path/to/</i>base-3.15.2</b>
<blockquote><pre>% <b>cd <i>/path/to/</i>base-3.15.3</b>
% <b>patch -p0 &lt; <i>/path/to/</i>file.patch</b></pre></blockquote>
<p>The following significant problems have been reported with this
@ -23,9 +23,10 @@ version of EPICS Base:</p>
<ul>
<li>Parallel builds ("make -j") on native Windows are not working properly.
Builds tend to hang (make saturating one core) - interrupting and calling make
again usually finishes the build. Sequential builds work and are recommended
for automated build environments.</li>
Builds tend to hang (saturating one core); interrupting and running make
again usually finishes the build. Limiting the number of parallel jobs using
something like "make -j8" also helps prevent this problem. Sequential builds
always work and are recommended for automated build environments.</li>
<li>64-bit Windows builds of the CAS library may not work with some compilers.
The code in <tt>src/legacy/gdd</tt> is currently incompatible with the LLP64

2
documentation/README.1st
View File

@ -1,6 +1,6 @@
Installation Instructions
EPICS Base Release 3.15.2
EPICS Base Release 3.15.3
--------------------------------------------------------------------------

2
documentation/README.html
View File

@ -9,7 +9,7 @@
<BODY>
<CENTER>
<H1>Installation Instructions</H1>
<H2>EPICS Base Release 3.15.2</H2><BR>
<H2>EPICS Base Release 3.15.3</H2><BR>
</CENTER>
<HR>
<H3> Table of Contents</H3>

8
documentation/RELEASE_NOTES.html
View File

@ -3,17 +3,19 @@
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
<title>EPICS Base R3.15.2 Release Notes</title>
<title>EPICS Base R3.15.3 Release Notes</title>
</head>
<body lang="en">
<h1 align="center">EPICS Base Release 3.15.2</h1>
<h1 align="center">EPICS Base Release 3.15.3</h1>
<p style="color:red">This version of EPICS Base has not been released yet.</p>
<h2 align="center">Changes between 3.15.1 and 3.15.2</h2>
<h2 align="center">Changes between 3.15.2 and 3.15.3</h2>
<!-- Insert new items immediately below here ... -->
<h2 align="center">Changes between 3.15.1 and 3.15.2</h2>
<h3>Raised limit on link field length in database files</h3>
<p>The length of INP/OUT link fields in database files was limited to 79 chars

64
documentation/ReleaseChecklist.html
View File

@ -60,11 +60,8 @@ responsible for these tasks in the past and are expected to continue in the
relevent roles unless the Release Manager designates otherwise:</p>
<dl>
<dt><strong>Release Manager</strong> (Andrew Johnson)</dt>
<dd>Responsible for the release</dd>
<dt><strong>Configuration Manager</strong> (Janet Anderson)</dt>
<dd>Responsible for committing version number updates and for
creating tarfiles</dd>
<dt><strong>Release Manager</strong> (Ralph Lange)</dt>
<dd>Responsible for managing and tagging the release</dd>
<dt><strong>Platform Developers</strong></dt>
<dd>Responsible for individual operating system platforms</dd>
<dt><strong>Application Developers</strong></dt>
@ -134,42 +131,42 @@ relevent roles unless the Release Manager designates otherwise:</p>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Release Manager</td>
<td>Edit and commit changes to the EPICS version number file
configure/CONFIG_BASE_VERSION.</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Release Manager</td>
<td>Tag the module in Bazaar, using these tag conventions:
<ul>
<li>
<tt>R3.15.2-pre<i>n</i></tt>
<tt>R3.15.3-pre<i>n</i></tt>
&mdash; pre-release tag
</li>
<li>
<tt>R3.15.2-rc<i>n</i></tt>
<tt>R3.15.3-rc<i>n</i></tt>
&mdash; release candidate tag, note the <tt>rc</tt> is now
lower-case</li>
</ul>
<blockquote><tt>
cd ~/base/mirror-3.15<br />
bzr tag R3.15.2-rc<i>n</i>
bzr tag R3.15.3-rc<i>n</i>
</tt></blockquote>
</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Release Manager</td>
<td>Export the tagged version into a tarfile. Note that this command
generates a gzipped tarfile directly from the repository:
<blockquote><tt>
cd ~/base<br />
bzr export --keywords=publish
--root=base-3.15.2-rc<i>n</i>
-r tag:R3.15.2-rc<i>n</i>
baseR3.15.2-rc<i>n</i>.tar.gz
mirror-3.15
--root=base-3.15.3-rc<i>n</i>
-r tag:R3.15.3-rc<i>n</i>
base-3.15.3-rc<i>n</i>.tar.gz
mirror-3.15
</tt></blockquote>
This requires that the Bazaar keywords plugin is installed and
configured properly.
@ -177,14 +174,15 @@ relevent roles unless the Release Manager designates otherwise:</p>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Release Manager</td>
<td>Test the tarfile by extracting its contents and building it on at
least one supported platform.</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Copy the tar file to the Base download area of the website.</td>
<td>Website Manager</td>
<td>If necessary recreate the tarfile following the instructions above.
Copy the tar file to the Base download area of the website</td>
</tr>
<tr>
<td>&nbsp;</td>
@ -223,13 +221,6 @@ relevent roles unless the Release Manager designates otherwise:</p>
<td>Run the CA client side regression tests on all available host
platforms.</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Platform Developers</td>
<td>Build and run the
<a href="https://launchpad.net/epics-base-tests">epics-base-tests</a>
suite on all available platforms.</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Platform Developers</td>
@ -279,32 +270,32 @@ relevent roles unless the Release Manager designates otherwise:</p>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Release Manager</td>
<td>Edit and commit changes to the EPICS version number file
configure/CONFIG_BASE_VERSION.</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Release Manager</td>
<td>Tag the module in Bazaar:
<blockquote><tt>
cd ~/base/mirror-3.15<br />
bzr tag R3.15.2</i>
bzr tag R3.15.3</i>
</tt></blockquote>
</td>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Release Manager</td>
<td>Export the tagged version into a tarfile. Note that this command
generates a gzipped tarfile directly from the repository:
<blockquote><tt>
cd ~/base<br />
bzr export --keywords=publish
--root=base-3.15.2
-r tag:R3.15.2
baseR3.15.2.tar.gz
mirror-3.15
--root=base-3.15.3
-r tag:R3.15.3
base-3.15.3.tar.gz
mirror-3.15
</tt></blockquote>
This requires that the Bazaar keywords plugin is installed and
configured properly.
@ -312,7 +303,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Release Manager</td>
<td>Test the tar file by extracting its contents and building it on at
least one supported platform</td>
</tr>
@ -321,8 +312,9 @@ relevent roles unless the Release Manager designates otherwise:</p>
</tr>
<tr>
<td>&nbsp;</td>
<td>Configuration Manager</td>
<td>Copy the tar file to the Base download area of the website</td>
<td>Website Manager</td>
<td>If necessary recreate the tarfile following the instructions above.
Copy the tar file to the Base download area of the website</td>
</tr>
<tr>
<td>&nbsp;</td>