Release 1.7.4 (#1200)

Author: cekees

RELEASE.md

@@ -1,15 +1,19 @@
-- To release a new version of proteus
-Update proteus/__init__.py (remove '.dev0' and increment version)
-Update setup.py (remove 'dev0' and increment version)
-Update doc/source/_templates/layout.html (added line for new release in pull down, set to default download to current release)
-rebuild docs and check docs
-  cd .. 
-  git clone https://github.com/erdc-cm/proteus proteus-website -b gh-pages
-  cd proteus
-  make docs
-When you are  satisified with both the current proteus commit and the docs commit and push proteus, and tag the release through the github releases site. Then commit the proteus-website gh-pages branch to publish the documentation on proteustoolkit.org
+# Releasing a new version of proteus
 
-- Switch back to dev
-
-Update proteus/__init__.py (add '.dev0' to version)
-Update setup.py (add '.dev0' to version)
+* Submit a PR with the following changes
+  * Create release candidate branch on your fork (e.g. rcX.Y.Z)
+  * Update proteus/__init__.py (remove '.dev0' and increment version)
+  * Update setup.py (remove 'dev0' and increment version)
+  * Update docs/Doxyfile (remove '.dev0' and increment version)
+  * Submit PR and request two reviewers
+  * Wait for it to be merged into master
+* Check the documentation generated by Travis from tests on master for any issues
+  * Clone erdc/proteus-docs
+  * Checkout master
+  * Open index.html in your browser and check the website (e.g. version numbers, math/diagram rendering)
+  * Merge master into gh-pages in the proteus-docs repo
+* Draft release on erdc/proteus
+  * List signficant changes and contributors since last release
+* Clean up
+  * Create devX.Y.Z branch
+    * Update the version numbers back to X.Y.Z.dev0

docs/Doxyfile

@@ -38,8 +38,7 @@ PROJECT_NAME           = proteus
 # could be handy for archiving the generated documentation or if some version
 # control system is used.
 
-PROJECT_NUMBER         = 1.7.3.dev0
-
+PROJECT_NUMBER         = 1.7.4
 # Using the PROJECT_BRIEF tag one can provide an optional one line description
 # for a project that appears at the top of each page and should give viewer a
 # quick idea about the purpose of the project. Keep the description short.

proteus/__init__.py

@@ -9,7 +9,7 @@
     import pkgutil
     __path__ = pkgutil.extend_path(__path__, __name__)
 
-__version__ = '1.7.3.dev0'
+__version__ = '1.7.4'
 
 __all__ = ["Archiver",
            "Domain",

proteus/mprans/RANS2P.py

@@ -2184,7 +2184,6 @@ def getJacobian(self, jacobian):
         argsDict["isActiveDOF"] = self.isActiveDOF
         self.rans2p.calculateJacobian(argsDict)
         assert(np.all(np.isfinite(jacobian.getCSRrepresentation()[2])))
-        print("norm jac ",np.linalg.norm(jacobian.getCSRrepresentation()[2]))
         if not self.forceStrongConditions and max(numpy.linalg.norm(self.u[1].dof, numpy.inf), numpy.linalg.norm(self.u[2].dof, numpy.inf), numpy.linalg.norm(self.u[3].dof, numpy.inf)) < 1.0e-8:
             self.pp_hasConstantNullSpace = True
         else:

setup.py

@@ -742,7 +742,7 @@ def __str__(self):
 
 def setup_given_extensions(extensions):
     setup(name='proteus',
-          version='1.7.3.dev0',
+          version='1.7.4',
           classifiers=[
               'Development Status :: 4 - Beta',
               'Environment :: Console',