HANDE - Revision history

Ghb29: /* Github releases */ typo

2020-02-20T00:51:15Z

Github releases: typo

← Older revision		Revision as of 00:51, 20 February 2020
Line 4:		Line 4:
	== Github releases ==		== Github releases ==

	Releases are pushed to [https://www.github.com/hande-~~qmn~~/hande ~~github~~] approx. every 6 months.		Releases are pushed to [https://www.github.com/hande-qmc/hande Github] approx. every 6 months.
	* Create a new file in the release_notes folder in the documentation, e.g. v1.4.rst, to describe what features have been added, changed, removed and what bugs have been fixed since the last release. Do this on a branch, ideally do a small pull request, merge to (private) master.		* Create a new file in the release_notes folder in the documentation, e.g. v1.4.rst, to describe what features have been added, changed, removed and what bugs have been fixed since the last release. Do this on a branch, ideally do a small pull request, merge to (private) master.
	* Ideally, recreate the benchmarks for the testsuite. To save time: do one run in optimised/non-debug mode, then do the debug tests. Or do all in debug mode. Need to be able to run the FCI tests. Again, doing this on a branch is probably cleanest.		* Ideally, recreate the benchmarks for the testsuite. To save time: do one run in optimised/non-debug mode, then do the debug tests. Or do all in debug mode. Need to be able to run the FCI tests. Again, doing this on a branch is probably cleanest.

Ajwt3: /* Running the test suite on cerebro */

2019-02-05T16:43:04Z

Running the test suite on cerebro

@@ Line 68: / Line 68: @@
 module unload hdf5
 module load hdf5/1.8.20/gcc-6.4.0
 </pre>

Van26: /* Github releases */

2019-02-05T16:38:16Z

Github releases

← Older revision		Revision as of 16:38, 5 February 2019
Line 5:		Line 5:

	Releases are pushed to [https://www.github.com/hande-qmn/hande github] approx. every 6 months.		Releases are pushed to [https://www.github.com/hande-qmn/hande github] approx. every 6 months.
	* Create a new file in the release_notes folder in the documentation, e.g. v1.4.rst, to describe what features have been added, changed, removed and what bugs have been fixed since the last release.		* Create a new file in the release_notes folder in the documentation, e.g. v1.4.rst, to describe what features have been added, changed, removed and what bugs have been fixed since the last release. Do this on a branch, ideally do a small pull request, merge to (private) master.
		⚫	* Ideally, recreate the benchmarks for the testsuite. To save time: do one run in optimised/non-debug mode, then do the debug tests. Or do all in debug mode. Need to be able to run the FCI tests. Again, doing this on a branch is probably cleanest.
	Do this on a branch, ideally do a small pull request, merge to (private) master.
⚫	* Ideally, recreate the benchmarks for the testsuite. To save time: do one run in optimised/non-debug mode, then do the debug tests. Or do all in debug mode. Need to be able to run the FCI tests.
	Again, doing this on a branch is probably cleanest.
	* Merge the public branch into the private master to keep a single history.		* Merge the public branch into the private master to keep a single history.
	* Update file `tools/configurator.py` to say the next version (e.g. 1.4 instead of 1.3).		* Update file `tools/configurator.py` to say the next version (e.g. 1.4 instead of 1.3).

Van26: /* Github releases */

2019-02-05T16:38:03Z

Github releases

← Older revision		Revision as of 16:38, 5 February 2019
Line 5:		Line 5:

	Releases are pushed to [https://www.github.com/hande-qmn/hande github] approx. every 6 months.		Releases are pushed to [https://www.github.com/hande-qmn/hande github] approx. every 6 months.
	- Create a new file in the release_notes folder in the documentation, e.g. v1.4.rst, to describe what features have been added, changed, removed and what bugs have been fixed since the last release.		* Create a new file in the release_notes folder in the documentation, e.g. v1.4.rst, to describe what features have been added, changed, removed and what bugs have been fixed since the last release.
	Do this on a branch, ideally do a small pull request, merge to (private) master.		Do this on a branch, ideally do a small pull request, merge to (private) master.
	- Ideally, recreate the benchmarks for the testsuite. To save time: do one run in optimised/non-debug mode, then do the debug tests. Or do all in debug mode. Need to be able to run the FCI tests.		* Ideally, recreate the benchmarks for the testsuite. To save time: do one run in optimised/non-debug mode, then do the debug tests. Or do all in debug mode. Need to be able to run the FCI tests.
	Again, doing this on a branch is probably cleanest.		Again, doing this on a branch is probably cleanest.
	- Merge the public branch into the private master to keep a single history.		* Merge the public branch into the private master to keep a single history.
	- Update file `tools/configurator.py` to say the next version (e.g. 1.4 instead of 1.3).		* Update file `tools/configurator.py` to say the next version (e.g. 1.4 instead of 1.3).
	- Tag this version as e.g. v1.4 (`git tag -a v1.4` - https://git-scm.com/book/en/v2/Git-Basics-Tagging).		* Tag this version as e.g. v1.4 (`git tag -a v1.4` - https://git-scm.com/book/en/v2/Git-Basics-Tagging).
	- Merge that updated private master into public master.		* Merge that updated private master into public master.
	- Update the hande-www repository to update the HANDE website. Update github documentation if required.		* Update the hande-www repository to update the HANDE website. Update github documentation if required.

	== Buildbot ==		== Buildbot ==

Van26: /* Github releases */

2019-02-05T16:37:17Z

Github releases

@@ Line 4: / Line 4: @@
 == Github releases ==
-Releases are pushed to [https://www.github.com/hande-qmn/hande github] approx. every 6 months.  Merge the public branch into the private master to keep a single history:
+Releases are pushed to [https://www.github.com/hande-qmn/hande github] approx. every 6 months.
 == Buildbot ==

Van26: /* Running the test suite on cerebro */

2018-05-08T15:59:06Z

Running the test suite on cerebro

← Older revision		Revision as of 15:59, 8 May 2018
Line 87:		Line 87:
	</pre>		</pre>

	Compile HANDE with these files modified ("git diff"):		Compile HANDE with these files modified ("git diff") using config/gfortran.mkl.mpi.pop64:
	<pre>		<pre>
	diff --git a/config/gfortran.mkl.mpi.pop64 b/config/gfortran.mkl.mpi.pop64		diff --git a/config/gfortran.mkl.mpi.pop64 b/config/gfortran.mkl.mpi.pop64

Van26 at 15:57, 8 May 2018

2018-05-08T15:57:23Z

@@ Line 1: / Line 1: @@
-Information about HANDE releases and suchlike.
+Information about HANDE releases and running tests.
@@ Line 54: / Line 54: @@
 <pre>
 nikola github_deploy
 </pre>

Van26 at 11:10, 10 April 2018

2018-04-10T11:10:25Z

← Older revision		Revision as of 11:10, 10 April 2018
Line 12:		Line 12:
	git config remote.github.push github-master:master		git config remote.github.push github-master:master

			git checkout master
	git merge github/master --strategy=ours		git merge github/master --strategy=ours
	git tag v1.3		git tag v1.3

Van26 at 11:08, 10 April 2018

2018-04-10T11:08:53Z

← Older revision		Revision as of 11:08, 10 April 2018
Line 8:		Line 8:
	<pre>		<pre>
	git remote add github git@github.com:hande-qmc/hande		git remote add github git@github.com:hande-qmc/hande
			git fetch github
	git checkout -tb github-master github/master		git checkout -tb github-master github/master
	git config remote.github.push github-master:master		git config remote.github.push github-master:master

	git merge github/master --strategy=ours		git merge github/master --strategy=ours
	git tag v1.2		git tag v1.3
	git co -B github-master		git co -B github-master
	git push		git push

Rstf2: Document some tasks related to HANDE

2017-01-30T13:48:11Z

Document some tasks related to HANDE

New page

Information about HANDE releases and suchlike.

== Github releases ==

Releases are pushed to [https://www.github.com/hande-qmn/hande github] approx. every 6 months. Merge the public branch into the private master to keep a single history:

<pre>
git remote add github git@github.com:hande-qmc/hande
git checkout -tb github-master github/master
git config remote.github.push github-master:master

git merge github/master --strategy=ours
git tag v1.2
git co -B github-master
git push
</pre>

(Remember to appropriately update the version information in environment_report.F90, and test benchmarks should also be regenerated prior to the release.)

In between releases, bug-fix commits from the private (development) repository are applied to the public branch (if the underlying bug is present in the public release):

<pre>
git rebase --preserve-merges --onto github-master HEAD^ HEAD
git co -B github-master
git push
</pre>

== Buildbot ==

The tests are run nightly by [http://www.cmth.ph.ic.ac.uk/buildbot/hande/grid buildbot]. To update the configuration, edit
<pre>
hande_master@zeeman.cmth.ph.ic.ac.uk:hande/master.cfg
</pre>

Remember to restart the buildbot afterwards:
<pre>
buildbot restart
</pre>

Other relevant accounts are the account the slaves connect to by ssh: hande@zeeman, and the account the CUC3 buildslave runs on: jss43@hypatia. This latter may need the buildslave restarted each time hypatia is rebooted:
<pre>
buildslave start
</pre>

== Website ==

The [http://www.hande.org.uk website] uses rst and Nikola. The source on [https://www.github.com/hande-qmc/hande-www github]. To update, edit the rst files (currently there is only a main page: to create others simply add more files to the pages/ folder), commit the changes and run
<pre>
nikola github_deploy
</pre>