Update version numbers for 3.15.8-DEV (3.15.7.1-DEV)

This commit is contained in:
Andrew Johnson
2019-10-31 15:23:11 -05:00
parent 74a90d141b
commit db4ad455d2
5 changed files with 38 additions and 32 deletions

View File

@@ -31,10 +31,10 @@ EPICS_MODIFICATION = 7
# EPICS_PATCH_LEVEL must be a number (win32 resource file requirement)
# Not included if zero
EPICS_PATCH_LEVEL = 0
EPICS_PATCH_LEVEL = 1
# This will end in -DEV between official releases
#EPICS_DEV_SNAPSHOT=-DEV
EPICS_DEV_SNAPSHOT=-DEV
#EPICS_DEV_SNAPSHOT=-pre1
#EPICS_DEV_SNAPSHOT=-pre1-DEV
#EPICS_DEV_SNAPSHOT=-pre2
@@ -43,7 +43,7 @@ EPICS_PATCH_LEVEL = 0
#EPICS_DEV_SNAPSHOT=-rc1-DEV
#EPICS_DEV_SNAPSHOT=-rc2
#EPICS_DEV_SNAPSHOT=-rc2-DEV
EPICS_DEV_SNAPSHOT=
#EPICS_DEV_SNAPSHOT=
# No changes should be needed below here

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.7</title>
<title>Known Problems in R3.15.8</title>
</head>
<body>
<h1 style="text-align: center">EPICS Base R3.15.7: Known Problems</h1>
<h1 style="text-align: center">EPICS Base R3.15.8: Known Problems</h1>
<p>Any patch files linked below should be applied at the root of the
base-3.15.7 tree. Download them, then use the GNU Patch program as
base-3.15.8 tree. Download them, then use the GNU Patch program as
follows:</p>
<blockquote><pre>% <b>cd <i>/path/to/</i>base-3.15.7</b>
<blockquote><pre>% <b>cd <i>/path/to/</i>base-3.15.8</b>
% <b>patch -p1 &lt; <i>/path/to/</i>file.patch</b></pre></blockquote>
<p>The following significant problems have been reported with this

View File

@@ -1,6 +1,6 @@
# Installation Instructions
## EPICS Base Release 3.15.7
## EPICS Base Release 3.15.8
-----
@@ -62,7 +62,7 @@ vendor's C and C++ compilers, as well as the GNU gcc and g++
compilers. The GNU cross-compilers work for all cross-compiled
targets. You may need the C and C++ compilers to be in your search
path to do EPICS builds; check the definitions of CC and CCC in
base/configure/os/CONFIG.&lt;host>.&lt;host> if you have problems.
`base/configure/os/CONFIG.<host>.<host>` if you have problems.
### <span id="0_0_6">Software requirements</span>
@@ -187,7 +187,7 @@ base/documentation directory of the distribution.
CONFIG Includes configure files and allows variable overrides
CONFIG.CrossCommon Cross build definitions
CONFIG.gnuCommon Gnu compiler build definitions for all archs
CONFIG_ADDONS Definitions for &lt;osclass> and DEFAULT options
CONFIG_ADDONS Definitions for <osclass> and DEFAULT options
CONFIG_APP_INCLUDE
CONFIG_BASE EPICS base tool and location definitions
CONFIG_BASE_VERSION Definitions for EPICS base version number
@@ -207,22 +207,22 @@ base/documentation directory of the distribution.
RULES_EXPAND
RULES_FILE_TYPE
RULES_TARGET
RULES_TOP Rules specific to a &lt;top> dir (uninstall and tar)
RULES_TOP Rules specific to a <top> dir (uninstall and tar)
Sample.Makefile Sample makefile with comments
```
#### base/configure/os directory - contains os-arch specific definitions
```
CONFIG.&lt;host>.&lt;target> Specific host-target build definitions
CONFIG.Common.&lt;target> Specific target definitions for all hosts
CONFIG.&lt;host>.Common Specific host definitions for all targets
CONFIG.<host>.<target> Specific host-target build definitions
CONFIG.Common.<target> Specific target definitions for all hosts
CONFIG.<host>.Common Specific host definitions for all targets
CONFIG.UnixCommon.Common Definitions for Unix hosts and all targets
CONFIG.Common.UnixCommon Definitions for Unix targets and all hosts
CONFIG.Common.vxWorksCommon Specific host definitions for all vx targets
CONFIG_SITE.&lt;host>.&lt;target> Site specific host-target definitions
CONFIG_SITE.Common.&lt;target> Site specific target defs for all hosts
CONFIG_SITE.&lt;host>.Common Site specific host defs for all targets
CONFIG_SITE.<host>.<target> Site specific host-target definitions
CONFIG_SITE.Common.<target> Site specific target defs for all hosts
CONFIG_SITE.<host>.Common Site specific host defs for all targets
```
### <span id="0_0_12">Building EPICS base (Unix and Win32)</span>
@@ -294,8 +294,8 @@ distribution file to be overridden except with CONFIG in the name
changed to `CONFIG_SITE`.
```
configure/os/CONFIG.&lt;host>.&lt;host> Host build settings
configure/os/CONFIG.&lt;host>.Common Host common build settings
configure/os/CONFIG.<host>.<host> Host build settings
configure/os/CONFIG.<host>.Common Host common build settings
```
**Target configuration**
@@ -307,8 +307,8 @@ replaced by `CONFIG_SITE`. This step is necessary even if the host
system is the only target system.
```
configure/os/CONFIG.Common.&lt;target> Target common settings
configure/os/CONFIG.&lt;host>.&lt;target> Host-target settings
configure/os/CONFIG.Common.<target> Target common settings
configure/os/CONFIG.<host>.<target> Host-target settings
```
#### Build EPICS base
@@ -351,7 +351,7 @@ the host system.
A perl script, makeBaseExt.pl, is included in the distribution file.
This script will create a sample extension that can be built and
executed. The makeBaseApp.pl and makeBaseExt.pl scripts are installed
into the install location bin/&lt;hostarch> directory during the base
into the install location `bin/<hostarch>` directory during the base
build.
### <span id="0_0_14">Multiple host platforms</span>
@@ -365,7 +365,7 @@ into the `$(INSTALL_LOCATION)/bin/<arch>` directories. Libraries are
installed into $`(INSTALL_LOCATION)/lib/<arch>`. The default
definition for `$(INSTALL_LOCATION)` is `$(TOP)` which is the root
directory in the distribution directory structure, base. Created
object files are stored in O.&lt;arch> source subdirectories, This
object files are stored in `O.<arch>` source subdirectories, This
allows objects for multiple cross target architectures to be
maintained at the same time. To build EPICS base for a specific
host/target combination you must have the proper host/target C/C++

View File

@@ -1,4 +1,10 @@
# EPICS Base Release 3.15.7
# EPICS Base Release 3.15.8
This version of EPICS Base has not been released yet.
## Changes made on the 3.15 branch since 3.15.7
<!-- Insert new items immediately below here ... -->
## Changes made between 3.15.6 and 3.15.7

View File

@@ -136,17 +136,17 @@ relevent roles unless the Release Manager designates otherwise:</p>
<td>Tag the module in Git, using these tag conventions:
<ul>
<li>
<tt>R3.15.7-pre1</tt>
<tt>R3.15.8-pre1</tt>
&mdash; pre-release tag
</li>
<li>
<tt>R3.15.7-rc1</tt>
<tt>R3.15.8-rc1</tt>
&mdash; release candidate tag
</li>
</ul>
<blockquote><tt>
cd base-3.15<br />
git tag -m 'ANJ: Tagged for 3.15.7-rc1' R3.15.7-rc1
git tag -m 'ANJ: Tagged for 3.15.8-rc1' R3.15.8-rc1
</tt></blockquote>
</td>
</tr>
@@ -158,11 +158,11 @@ relevent roles unless the Release Manager designates otherwise:</p>
files and directories that are only used for continuous integration:
<blockquote><tt>
cd base-3.15<br />
git archive --prefix=base-3.15.7-rc1/ --output=base-3.15.7-rc1.tar.gz R3.15.7-rc1 configure documentation LICENSE Makefile README src startup
git archive --prefix=base-3.15.8-rc1/ --output=base-3.15.8-rc1.tar.gz R3.15.8-rc1 configure documentation LICENSE Makefile README src startup
</tt></blockquote>
Create a GPG signature file of the tarfile as follows:
<blockquote><tt>
gpg --armor --sign --detach-sig base-3.15.7-rc1.tar.gz
gpg --armor --sign --detach-sig base-3.15.8-rc1.tar.gz
</tt></blockquote>
</td>
</tr>
@@ -274,7 +274,7 @@ relevent roles unless the Release Manager designates otherwise:</p>
<td>Tag the module in Git:
<blockquote><tt>
cd base-3.15<br />
git tag -m 'ANJ: Tagged for 3.15.7' R3.15.7
git tag -m 'ANJ: Tagged for 3.15.8' R3.15.8
</tt></blockquote>
</td>
</tr>
@@ -285,11 +285,11 @@ relevent roles unless the Release Manager designates otherwise:</p>
generates a gzipped tarfile directly from the repository:
<blockquote><tt>
cd base-3.15<br />
git archive --prefix=base-3.15.7/ --output=base-3.15.7.tar.gz R3.15.7 configure documentation LICENSE Makefile README src startup
git archive --prefix=base-3.15.8/ --output=base-3.15.8.tar.gz R3.15.8 configure documentation LICENSE Makefile README src startup
</tt></blockquote>
Create a GPG signature file of the tarfile as follows:
<blockquote><tt>
gpg --armor --sign --detach-sig base-3.15.7.tar.gz
gpg --armor --sign --detach-sig base-3.15.8.tar.gz
</tt></blockquote>
</td>
</tr>