Preparing for new release 2.10.1

This commit is contained in:
Rob Falgout 2015-09-11 10:24:45 -07:00
parent 7a540c53d5
commit 8b2efbf182
6 changed files with 209 additions and 15 deletions

View File

@ -15,6 +15,8 @@
# recent release.
#=============================================================================
Version 2.10.1 released 2015/09/11
- Fixed various bugs in AMG and the IJ interface.
- Changed function names to set interpolation truncation parameters for

View File

@ -2,8 +2,8 @@ cmake_minimum_required (VERSION 2.8.8)
project (hypre)
# The version number.
set (HYPRE_VERSION 2.10.0b)
set (HYPRE_DATE 2015/01/22)
set (HYPRE_VERSION 2.10.1)
set (HYPRE_DATE 2015/09/11)
set (HYPRE_TIME 00:00:00)
set (HYPRE_BUGS hypre-support@llnl.gov)
set (HYPRE_SRCDIR "${PROJECT_SOURCE_DIR}")

View File

@ -55,8 +55,8 @@ dnl * Set package information so it only has to be modified in one place
dnl *********************************************************************
m4_define([M4_HYPRE_NAME], [hypre])
m4_define([M4_HYPRE_VERSION], [2.10.0b])
m4_define([M4_HYPRE_DATE], [2015/01/22])
m4_define([M4_HYPRE_VERSION], [2.10.1])
m4_define([M4_HYPRE_DATE], [2015/09/11])
m4_define([M4_HYPRE_TIME], [00:00:00])
m4_define([M4_HYPRE_BUGS], [hypre-support@llnl.gov])
m4_define([M4_HYPRE_SRCDIR], [`pwd`])

22
configure vendored
View File

@ -1,7 +1,7 @@
#! /bin/sh
# From configure.in Id.
# Guess values for system-dependent variables and create Makefiles.
# Generated by GNU Autoconf 2.63 for hypre 2.10.0b.
# Generated by GNU Autoconf 2.63 for hypre 2.10.1.
#
# Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
# 2002, 2003, 2004, 2005, 2006, 2007, 2008 Free Software Foundation, Inc.
@ -603,8 +603,8 @@ SHELL=${CONFIG_SHELL-/bin/sh}
# Identity of this package.
PACKAGE_NAME='hypre'
PACKAGE_TARNAME='hypre'
PACKAGE_VERSION='2.10.0b'
PACKAGE_STRING='hypre 2.10.0b'
PACKAGE_VERSION='2.10.1'
PACKAGE_STRING='hypre 2.10.1'
PACKAGE_BUGREPORT=''
ac_unique_file="HYPRE.h"
@ -1333,7 +1333,7 @@ if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
cat <<_ACEOF
\`configure' configures hypre 2.10.0b to adapt to many kinds of systems.
\`configure' configures hypre 2.10.1 to adapt to many kinds of systems.
Usage: $0 [OPTION]... [VAR=VALUE]...
@ -1398,7 +1398,7 @@ fi
if test -n "$ac_init_help"; then
case $ac_init_help in
short | recursive ) echo "Configuration of hypre 2.10.0b:";;
short | recursive ) echo "Configuration of hypre 2.10.1:";;
esac
cat <<\_ACEOF
@ -1586,7 +1586,7 @@ fi
test -n "$ac_init_help" && exit $ac_status
if $ac_init_version; then
cat <<\_ACEOF
hypre configure 2.10.0b
hypre configure 2.10.1
generated by GNU Autoconf 2.63
Copyright (C) 1992, 1993, 1994, 1995, 1996, 1998, 1999, 2000, 2001,
@ -1608,7 +1608,7 @@ cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by hypre $as_me 2.10.0b, which was
It was created by hypre $as_me 2.10.1, which was
generated by GNU Autoconf 2.63. Invocation command line was
$ $0 $@
@ -2016,8 +2016,8 @@ ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var.
HYPRE_NAME="hypre"
HYPRE_VERSION="2.10.0b"
HYPRE_DATE="2015/01/22"
HYPRE_VERSION="2.10.1"
HYPRE_DATE="2015/09/11"
HYPRE_TIME="00:00:00"
HYPRE_BUGS="hypre-support@llnl.gov"
HYPRE_SRCDIR="`pwd`"
@ -8522,7 +8522,7 @@ exec 6>&1
# report actual input values of CONFIG_FILES etc. instead of their
# values after options handling.
ac_log="
This file was extended by hypre $as_me 2.10.0b, which was
This file was extended by hypre $as_me 2.10.1, which was
generated by GNU Autoconf 2.63. Invocation command line was
CONFIG_FILES = $CONFIG_FILES
@ -8581,7 +8581,7 @@ Report bugs to <bug-autoconf@gnu.org>."
_ACEOF
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_version="\\
hypre config.status 2.10.0b
hypre config.status 2.10.1
configured by $0, generated by GNU Autoconf 2.63,
with options \\"`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`\\"

96
releases/check2.10.1.txt Normal file
View File

@ -0,0 +1,96 @@
HYPRE Release Checklist
Releases are given a number of the form MAJOR.MINOR.PATCH, where an increment in
one of the digits denotes the following (in general):
MAJOR - backward incompatible release (API changes)
MINOR - new features
PATCH - bug fixes or other trivial changes
See the Developer's Manual for more information on creating new releases.
The following steps must be completed, initialed and dated on the [] line by the
responsible project member before the release is made available to users. Some
of the steps are optional for PATCH and MINOR releases (as indicated below).
- Decision made for release number 2.10.1
[rdf 5/1/2015] MAJOR.MINOR.PATCH
- Copy this file to 'check{release number}.txt'.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
- Create a tracker issue "New hypre release {number}" advising project personnel
of release decision and tentative date with a request to not disrupt the
repository until the release is complete.
[rdf 5/1/2015] MAJOR.MINOR.PATCH
- Initial documentation review meeting.
[] MAJOR
- Update user, reference, and developer manuals with information regarding
contents of this release.
[] MAJOR.MINOR
- Final documentation review meeting.
[] MAJOR
- Update 'CHANGELOG' file with information regarding contents of this release.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
- Verify that all agreed-upon changes have been committed.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
- Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
[rdf 9/11/2015] MAJOR.MINOR.PATCH
- Tag repository with release number: git tag -a V2-0-0 -m "Release 2.0.0".
Push the tags to the central repository: git push --tags
[] MAJOR.MINOR.PATCH
- Create release tar files by running the 'tools/mkdist' script (for more
information, do 'mkdist -help'). This can be run from within any directory,
just be sure to use the latest version of the 'mkdist' script.
[] MAJOR.MINOR.PATCH
- Run the 'AUTOTEST/testdist.sh' script to verify a stable release. For more
information on running this script, do 'testdist.sh -help'. If any of the
tests fail, untag the repository, make necessary corrections, and start over.
[] MAJOR.MINOR.PATCH
- Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
[] MAJOR.MINOR.PATCH
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[] MAJOR.MINOR.PATCH
- On the RZ, copy tar file to '/usr/gapps/hypre' (for backup reasons).
[] MAJOR.MINOR.PATCH
- Put release on download page, and inform project team and other appropriate
users of availability.
[] MAJOR.MINOR.PATCH
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository.
[] MAJOR.MINOR.PATCH

96
releases/checklist.txt Normal file
View File

@ -0,0 +1,96 @@
HYPRE Release Checklist
Releases are given a number of the form MAJOR.MINOR.PATCH, where an increment in
one of the digits denotes the following (in general):
MAJOR - backward incompatible release (API changes)
MINOR - new features
PATCH - bug fixes or other trivial changes
See the Developer's Manual for more information on creating new releases.
The following steps must be completed, initialed and dated on the [] line by the
responsible project member before the release is made available to users. Some
of the steps are optional for PATCH and MINOR releases (as indicated below).
- Decision made for release number X.X.X
[fml m/d/yyyy] MAJOR.MINOR.PATCH
- Copy this file to 'check{release number}.txt'.
[] MAJOR.MINOR.PATCH
- Create a tracker issue "New hypre release {number}" advising project personnel
of release decision and tentative date with a request to not disrupt the
repository until the release is complete.
[] MAJOR.MINOR.PATCH
- Initial documentation review meeting.
[] MAJOR
- Update user, reference, and developer manuals with information regarding
contents of this release.
[] MAJOR.MINOR
- Final documentation review meeting.
[] MAJOR
- Update 'CHANGELOG' file with information regarding contents of this release.
[] MAJOR.MINOR.PATCH
- Verify that all agreed-upon changes have been committed.
[] MAJOR.MINOR.PATCH
- Update 'config/configure.in' and 'CMakeLists.txt' with release number and
date, then run 'config/bootstrap' and commit changes to the repository.
[] MAJOR.MINOR.PATCH
- Tag repository with release number: git tag -a V2-0-0 -m "Release 2.0.0".
Push the tags to the central repository: git push --tags
[] MAJOR.MINOR.PATCH
- Create release tar files by running the 'tools/mkdist' script (for more
information, do 'mkdist -help'). This can be run from within any directory,
just be sure to use the latest version of the 'mkdist' script.
[] MAJOR.MINOR.PATCH
- Run the 'AUTOTEST/testdist.sh' script to verify a stable release. For more
information on running this script, do 'testdist.sh -help'. If any of the
tests fail, untag the repository, make necessary corrections, and start over.
[] MAJOR.MINOR.PATCH
- Commit the verification file generated by the 'testdist.sh' script into the
releases/ directory of the repository.
[] MAJOR.MINOR.PATCH
- On the CASC cluster, copy tar file to '/usr/casc/hypre'.
[] MAJOR.MINOR.PATCH
- On the RZ, copy tar file to '/usr/gapps/hypre' (for backup reasons).
[] MAJOR.MINOR.PATCH
- Put release on download page, and inform project team and other appropriate
users of availability.
[] MAJOR.MINOR.PATCH
- FINAL CERTIFICATION: Verify that all steps have been signed off and commit
this file to the repository.
[] MAJOR.MINOR.PATCH