Skip to content
Snippets Groups Projects
Commit e1e296ca authored by Andreas Marek's avatar Andreas Marek
Browse files

Prepare release of ELPA 2017.05.002

parent e2ab51c3
No related branches found
No related tags found
No related merge requests found
Changelog for ELPA 2017.05.002
Mainly bugfixes for ELPA 2017.05.001:
- fix memory leak of MPI communicators
- tests for hermitian_multiply, cholesky decomposition and
- deal with a problem on Debian (mawk)
Changelog for ELPA 2017.05.001
Final release of ELPA 2017.05.001
Since rc2 the following changes have been made
- more extensive tests during "make check"
- distribute missing C headers
- introduce analytic tests
- Fix stack overflow in some kernels
Changelog for ELPA 2017.05.001.rc2
This is the release candidate 2 for the ELPA 2017.05.001 version.
......
......@@ -6,7 +6,7 @@ in the (near) future from the *ELPA* library.
### A) Deprecated interfaces:###
With the release of ELPA 2017.05.001.rc1 a new, more general API for the library has
With the release of ELPA 2017.05.001 a new, more general API for the library has
been published. All new features of ELPA will only be accesible via this new interface.
For ease of transion, the API as defined in release ELPA 2016.11.001 has been frozen in
and will be still supported for some time, albeit without any new features.
......
......@@ -2,7 +2,7 @@
## Preamle ##
This file provides documentation on how to build the *ELPA* library in **version ELPA-2017.05.001**.
This file provides documentation on how to build the *ELPA* library in **version ELPA-2017.05.002**.
With release of **version ELPA-2017.05.001** the build process has been significantly simplified,
which makes it easier to install the *ELPA* library
......
......@@ -6,6 +6,9 @@ Issues which are not mentioned in a newer release are (considered as) solved
### ELPA 2017.05.001 release ###
- at the moment no issues are known
### ELPA 2017.05.001 release ###
- accidently a memory leak has been introduced
### ELPA 2017.05.001.rc2 release ###
- compilation with Intel Compiler 2018 beta does not work
(see https://gitlab.mpcdf.mpg.de/elpa/elpa/issues/54)
......
......@@ -67,4 +67,9 @@ https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
However, a new, more general API has been published, which will in the long run
completely replace the "legacy" interface.
The state of release 2017.05.001.rc1 defines this interface
The state of release 2017.05.001 defines this interface
- 10
NO incompatible API changes w.r.t. to the previous version. Only some functions have
been added. The state of release 2017.05.001 defines this interface
......@@ -2,7 +2,7 @@
## Current Release ##
The current release is ELPA 2017.05.001. The current supported API version
The current release is ELPA 2017.05.002. The current supported API version
is 20170403. This release supports the earliest API version 20170403.
## About *ELPA*
......
This file contains the release notes for the ELPA 2017.05.001.rc1 version
This file contains the release notes for the ELPA 2017.05.002 version
What is new?
-------------
......
......@@ -151,7 +151,7 @@ Local documentation (via man pages) should be available (if *ELPA* has been inst
For example "man elpa2_print_kernels" should provide the documentation for the *ELPA* program which prints all
the available kernels.
Also a [online doxygen documentation] (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2017.05.001/html/index.html)
Also a [online doxygen documentation] (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2017.05.002/html/index.html)
for each *ELPA* release is available.
......@@ -9,14 +9,13 @@ Local documentation (via man pages) should be available (if *ELPA* has been inst
For example "man elpa2_print_kernels" should provide the documentation for the *ELPA* program which prints all
the available kernels.
Also a [online doxygen documentation] (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2017.05.001/html/index.html)
Also a [online doxygen documentation] (http://elpa.mpcdf.mpg.de/html/Documentation/ELPA-2017.05.002/html/index.html)
for each *ELPA* release is available.
## API of the *ELPA* library ##
With release 2017.05.001.rc1 of the *ELPA* library the interface has been rewritten substantially, in order to have a more
generic interface and to avoid future interface changes.
With release 2017.05.001 of the *ELPA* library the interface has been rewritten substantially, in order to have a more generic interface and to avoid future interface changes.
For compatibility reasons the interface defined in the previous release 2016.11.001 is also still available
IF AND ONLY IF *ELPA* has been build with support of this legacy interface.
......@@ -24,7 +23,7 @@ IF AND ONLY IF *ELPA* has been build with support of this legacy interface.
If you want to use the legacy interface, please look to section "B) Using the legacy API of the *ELPA* library.
The legacy API defines all the functionallity as it has been defined in *ELPA* release 2016.11.011. Note, however,
that all future features of *ELPA* will only be accessible via the new API defined in release 2017.05.001.rc1 or later.
that all future features of *ELPA* will only be accessible via the new API defined in release 2017.05.001 or later.
## A) Using the final API definition of the *ELPA* library ##
......
......@@ -1035,10 +1035,8 @@ m4_foreach_w([elpa_m4_kind],[real complex],[
#echo " "
#echo "***********************************************************************"
#echo "* This is a the release candidate ELPA 2017.05.001.rc2 *"
#echo "* All functionality of the release ELPA 2017.05.001 is already there.*"
#echo "* This release candidate reflects, except for maybe smaller bug *"
#echo "* corrections, the release of ELPA 2017.05.001 *"
#echo "* This is a the release of ELPA 2017.05.002 *"
#echo "* It mainly contains bugfixes to ELPA 2017.05.001 *"
#echo "***********************************************************************"
#echo " "
make -f $srcdir/generated_headers.am generated-headers top_srcdir="$srcdir"
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment