Any patch files linked below should be applied at the root of the -base-3.15.3 tree. Download them, then use the GNU Patch program as +base-3.15.5 tree. Download them, then use the GNU Patch program as follows:
-% cd /path/to/base-3.15.3 +% cd /path/to/base-3.15.5 % patch -p0 < /path/to/file.patchThe following significant problems have been reported with this @@ -22,22 +22,11 @@ version of EPICS Base:
-
diff --git a/documentation/README.1st b/documentation/README.1st index e82263d67..8349d445c 100644 --- a/documentation/README.1st +++ b/documentation/README.1st @@ -1,6 +1,6 @@ Installation Instructions - EPICS Base Release 3.15.3 + EPICS Base Release 3.15.5 -------------------------------------------------------------------------- diff --git a/documentation/README.html b/documentation/README.html index 56aa27528..eef83ed58 100644 --- a/documentation/README.html +++ b/documentation/README.html @@ -9,7 +9,7 @@- See LaunchPad bug - #1466129: - The feature that allows an IOC to bind to a single network interface is not - working correctly. The bug mentioned above contains a patch that has been - tested on Linux-64, a complete fix is expected for 3.15.4. Note that Windows - systems are not affected by this bug.
- -- Parallel builds ("make -j") on native Windows are not working properly. - 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.
- -- 64-bit Windows builds of the CAS library may not work with some compilers. - The code in src/legacy/gdd is currently incompatible with the LLP64 - model that Windows uses for its 64-bit ABI.
+- Parallel builds ("make -j") of Windows DLL targets don't work, because the + build rules don't contain all the necessary dependencies. This problem has + been fixed in the 3.15 series build rules, but will not be addressed in the + 3.14 branch. Sequential builds always work and are recommended for automated + build environments.
Installation Instructions
-EPICS Base Release 3.15.3
+EPICS Base Release 3.15.5
Table of Contents
diff --git a/documentation/ReleaseChecklist.html b/documentation/ReleaseChecklist.html index 085b22047..49d936ca2 100644 --- a/documentation/ReleaseChecklist.html +++ b/documentation/ReleaseChecklist.html @@ -135,17 +135,17 @@ relevent roles unless the Release Manager designates otherwise:Tag the module in Bazaar, using these tag conventions: @@ -156,10 +156,10 @@ relevent roles unless the Release Manager designates otherwise: generates a gzipped tarfile directly from the repository:
- - R3.15.3-pren + R3.15.5-pren — pre-release tag
- - R3.15.3-rcn + R3.15.5-rcn — release candidate tag, note the rc is now lower-case
cd ~/base/mirror-3.15
- bzr tag R3.15.3-rcn + bzr tag R3.15.5-rcncd ~/baseThis requires that the Bazaar keywords plugin is installed and @@ -274,7 +274,7 @@ relevent roles unless the Release Manager designates otherwise:
- bzr export --keywords=publish - --root=base-3.15.3-rcn - -r tag:R3.15.3-rcn - base-3.15.3-rcn.tar.gz + bzr export + --root=base-3.15.5-rcn + -r tag:R3.15.5-rcn + base-3.15.5-rcn.tar.gz mirror-3.15Tag the module in Bazaar: @@ -285,10 +285,10 @@ relevent roles unless the Release Manager designates otherwise: generates a gzipped tarfile directly from the repository:cd ~/base/mirror-3.15
- bzr tag R3.15.3 + bzr tag R3.15.5cd ~/baseThis requires that the Bazaar keywords plugin is installed and
- bzr export --keywords=publish - --root=base-3.15.3 - -r tag:R3.15.3 - base-3.15.3.tar.gz + bzr export + --root=base-3.15.5 + -r tag:R3.15.5 + base-3.15.5.tar.gz mirror-3.15