[open-coarrays] 52/80: Add .VERSION file to repo
Alastair McKinstry
mckinstry at moszumanska.debian.org
Wed Oct 25 13:45:49 UTC 2017
This is an automated email from the git hooks/post-receive script.
mckinstry pushed a commit to branch debian/master
in repository open-coarrays.
commit c022b78ae40e39a34e153b9f6ced6896aa90b6e6
Author: Alastair McKinstry <mckinstry at debian.org>
Date: Thu Apr 20 12:31:42 2017 +0100
Add .VERSION file to repo
---
.VERSION | 5 ++
.github/ISSUE_TEMPLATE.md | 138 +++++++++++++++++++++++++++++++++++++++
.github/PULL_REQUEST_TEMPLATE.md | 76 +++++++++++++++++++++
3 files changed, 219 insertions(+)
diff --git a/.VERSION b/.VERSION
new file mode 100644
index 0000000..eaad759
--- /dev/null
+++ b/.VERSION
@@ -0,0 +1,5 @@
+# OpenCoarrays version file. Odd patch levels indicate inter-release
+# version, i.e., code is from SCM/git. This project uses semantic
+# versioning. For details see http://semver.org
+
+1.8.6
diff --git a/.github/ISSUE_TEMPLATE.md b/.github/ISSUE_TEMPLATE.md
new file mode 100644
index 0000000..a0ed192
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE.md
@@ -0,0 +1,138 @@
+<!-- Please fill out the issue template included below, failure to do -->
+<!-- so may result in immediate closure of your issue. -->
+
+<!-- Fill out all portions of this template that apply. Please delete -->
+<!-- any unnecessary sections. -->
+
+| Avg response time |
+| ------------------------------ |
+| ![Issue Stats][issue stat img] |
+
+Please replace `[ ]` with `[X]` to indicate you have taken the requested action
+
+ - [ ] I have surrounded any code, or log output in codeblock fences
+ (` ``` `) if it occupies more than one line, or in single
+ backticks if it is short `short code`
+
+<!-- Long code goes in a fenced code block: -->
+<!-- ``` -->
+<!-- Line one of code output -->
+<!-- Line two of output -->
+<!-- etc. -->
+<!-- ``` -->
+
+
+# Question: #
+
+<!-- delete this section if it does not apply -->
+The title of the issue should start with `Question:` followed by a
+succinct title. Add the text of your question here. Be specific. Search for
+answers on https://google.com and https://stackoverflow.com
+before asking a new question
+
+# RFE: #
+
+<!-- delete this section if it does not apply -->
+The title of the issue should start with `RFE:` followed by a succinct
+title. Add a description of your requested enhancement here. If you are
+willing to help out please also read the [Helping Out] section of
+[CONTRIBUTING.md]
+
+
+
+# Defect/bug report #
+
+<!-- delete this section if it does not apply -->
+The title of the issue should start with `Defect:` followed by a
+succinct title.
+
+ - [ ] I have searched the [issues page] and [mailing list] and did
+ not find any issue matching the one I would like to report
+ - [ ] I have included a succinct description of the problem,
+ including the steps necessary to reproduce it
+ - [ ] I have included which version of OpenCoarrays I am working
+ with, or the output of `git describe` if working with a cloned
+ repository rather than an [official release]
+ - [ ] I have included the MPI library name and version I am using
+ with OpenCoarrays
+ - [ ] name: [MPICH] version:
+ - [ ] name: [Open-MPI] version:
+ - [ ] name: [MVAPICH] version:
+ - [ ] name: [MPT] version:
+ - [ ] name: [Intel MPI] version:
+ - [ ] other:
+ <!-- delete all but the matching MPI implementation -->
+ - [ ] I have included the Fortran compiler name and version that I am
+ using with OpenCoarrays
+ - [ ] I have included the output of `uname -a`
+ - [ ] I have included the Operating system name and version,
+ including linux distro
+ - [ ] I have included the machine name if I am allowed to do so and
+ wish to seek help debugging on that particular system (Titan,
+ Pleiades, Excalibur, Lightening, Mira, etc.)
+
+## Installation/build problem ##
+
+<!-- delete this section if it does not apply -->
+
+ - [ ] I have attached a log of the attempted build/installation,
+ changing the extension to `.txt` and uploaded it to this issue
+ - [ ] I have indicated if previous versions of OpenCoarrays are or
+ were installed on the machine in question
+
+**Please select one from the following top level items** (please be sure to fill out all sub-items)**:**
+ - [ ] Build/install was attempted with [install.sh]
+ - [ ] I have attached the `install-opencoarrays.log` file
+ after re-running the script with the debug flags `-d` and
+ `-v` turned on (after renaming the log file to have a `.txt`
+ extension)
+ - [ ] Build/install was attempted with system package manager like
+ [homebrew] (which one?)
+ - [ ] Build/install was attempted with manual/advanced
+ [CMake install]
+ - [ ] Name and version of the C compiler being used
+ - [ ] Name and version of the Fortran compiler being used
+ - [ ] Attached/included the output of the configure step with
+ CMake. (Usually something like `cd build && cmake ..`)
+ - [ ] Attached/included the output of `make VERBOSE=1`
+ - [ ] Attached/included the output of `ctest --verbose`
+ - [ ] Other build/install was attempted (please describe)
+
+Don't forget the description of the problem. The more details you give
+us, the faster, and more easily we can help you
+
+## Compile time or run time error
+
+<!-- delete this section if it does not apply -->
+
+**Please choose one of the first two items**
+ - [ ] I am experiencing a compile time error (all gfortran ICEs
+ should be reported to the [GFortran bug tracker]... You can post
+ the ICE here too for tracking purposes, with a link to the
+ GFortran problem report)
+ - [ ] I am experiencing a runtime issue
+
+**:sparkles: Optional, but you will receive infinite karma for including this: :sparkles:**
+ - [ ] I have included a minimally complete verifiable example (MCVE)
+ that exhibits the problem and suitable for adding to regression
+ tests
+
+Don't forget a description with as many details as possible to reproduce the problem.
+
+
+[links]:#
+[GFortran bug tracker]: https://gcc.gnu.org/bugzilla/
+[Intel MPI]: https://software.intel.com/en-us/intel-mpi-library
+[MPT]: http://www.sgi.com/products/software/sps.html
+[MVAPICH]: http://mvapich.cse.ohio-state.edu
+[MPICH]: https://www.mpich.org
+[Open-MPI]: https://www.open-mpi.org
+[CONTRIBUTING.md]: https://github.com/sourceryinstitute/OpenCoarrays/blob/master/CONTRIBUTING.md
+[Helping Out]: https://github.com/sourceryinstitute/OpenCoarrays/blob/master/CONTRIBUTING.md#helping-out
+[official release]: https://github.com/sourceryinstitute/OpenCoarrays/releases
+[CMake install]: https://github.com/sourceryinstitute/OpenCoarrays/blob/master/INSTALL.md#cmake-scripts
+[homebrew]: http://brew.sh
+[issues page]: https://github.com/sourceryinstitute/OpenCoarrays/issues
+[mailing list]: https://groups.google.com/forum/#!forum/opencoarrays
+[install.sh]: https://github.com/sourceryinstitute/OpenCoarrays/blob/master/install.sh
+[issue stat img]:https://img.shields.io/issuestats/i/github/sourceryinstitute/OpenCoarrays.svg?style=flat-square
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 0000000..0019763
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,76 @@
+<!-- Please fill out the pull request template included below, failure -->
+<!-- to do so may result in immediate closure of your pull request. -->
+
+<!-- Fill out all portions of this template that apply. Please delete -->
+<!-- any unnecessary sections. -->
+
+| Avg response time | coverage on master |
+| --------------------------------- | ---------------------------|
+| ![Issue Stats][PR response img] | ![Codecov branch][coverage]|
+
+## Summary of changes ##
+
+Summarize what you changed
+
+## Rationale for changes ##
+
+Why did you make these changes?
+
+## Additional info and certifications ##
+
+This pull request (PR) is a:
+ - [ ] Bug fix
+ - [ ] Feature addition
+ - [ ] Other, Please describe:
+
+I certify that:
+
+ - [ ] I have reviewed the [contributing guidelines]
+ - [ ] If this PR is a work in progress I have added `WIP:` to the
+ beginning of the PR title
+ - [ ] If this PR is problematic for any reason, I have added
+ `DO NOT MERGE:` to the beginning of the title
+ - [ ] The branch name and title of this PR contains the text
+ `issue-<#>` where `<#>` is replaced by the issue that this PR
+ is addressing
+ - [ ] I have deleted trailing white space on any lines that this PR
+ touches
+ - [ ] I have used spaces for indentation on any lines that this PR
+ touches
+ - [ ] I have included some comments to explain non-obvious code
+ changes
+ - [ ] I have run the tests localy (`ctest`) and all tests pass
+ - [ ] Each commit is a logically atomic, self-consistent, cohesive
+ set of changes
+ - [ ] The [commit message] should follow [these guidelines]:
+ - [ ] First line is directive phrase, starting with a capitalized
+ imperative verb, and is no longer than 50 characters
+ summarizing your commit
+ - [ ] Next line, if necessary is blank
+ - [ ] Following lines are all wrapped at 72 characters and can
+ include additional paragraphs, bulleted lists, etc.
+ - [ ] Use [Github keywords] where appropriate, to indicate the
+ commit resolves an open issue.
+ - [ ] I have signed [Contributor License Agreement (CLA)] by
+ clicking the "details" link to the right of the `licence/cla`
+ check and following the directions on the CLA assistant webpage
+ - [ ] I have ensured that the test coverage hasn't gone down and added new [unit tests] to cover an new code added to the library
+
+
+## For contributors and SI team members with code review priviledges ##
+
+ - [ ] I certify that I will wait 24 hours before self-approving via
+ [pullapprove comment] or [Github code review] so that someone
+ else has the chance to review my proposed changes
+
+[links]:#
+[contributing guidelines]: https://github.com/sourceryinstitute/OpenCoarrays/blob/master/CONTRIBUTING.md
+[commit message]: https://robots.thoughtbot.com/5-useful-tips-for-a-better-commit-message
+[these guidelines]: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html
+[Contributor License Agreement (CLA)]: https://cla-assistant.io/sourceryinstitute/OpenCoarrays
+[pullapprove comment]: https://pullapprove.com/sourceryinstitute/OpenCoarrays/settings/
+[Github code review]: https://help.github.com/articles/about-pull-request-reviews/
+[Github keywords]: https://help.github.com/articles/closing-issues-via-commit-messages/
+[unit tests]: https://github.com/sourceryinstitute/OpenCoarrays/tree/master/src/tests/unit
+[PR response img]: https://img.shields.io/issuestats/p/github/sourceryinstitute/OpenCoarrays.svg?style=flat-square
+[coverage]: https://img.shields.io/codecov/c/github/sourceryinstitute/OpenCoarrays/master.svg?style=flat-square
--
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/debian-science/packages/open-coarrays.git
More information about the debian-science-commits
mailing list