New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
3_support_bug.md in trunk/NEMOGCM/TOOLS/SIREN/src/docsrc – NEMO

source: trunk/NEMOGCM/TOOLS/SIREN/src/docsrc/3_support_bug.md @ 7646

Last change on this file since 7646 was 7646, checked in by timgraham, 7 years ago

Merge of dev_merge_2016 into trunk. UPDATE TO ARCHFILES NEEDED for XIOS2.
LIM_SRC_s/limrhg.F90 to follow in next commit due to change of kind (I'm unable to do it in this commit).
Merged using the following steps:

1) svn merge --reintegrate ​svn+ssh://forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/trunk .
2) Resolve minor conflicts in sette.sh and namelist_cfg for ORCA2LIM3 (due to a change in trunk after branch was created)
3) svn commit
4) svn switch ​svn+ssh://forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/trunk
5) svn merge ​svn+ssh://forge.ipsl.jussieu.fr/ipsl/forge/projets/nemo/svn/branches/2016/dev_merge_2016 .
6) At this stage I checked out a clean copy of the branch to compare against what is about to be committed to the trunk.
6) svn commit #Commit code to the trunk

In this commit I have also reverted a change to Fcheck_archfile.sh which was causing problems on the Paris machine.
File size: 1.2 KB
Line 
1# Support
2
3# How to get support
4  If you have questions regarding the use of SIREN, please have a look at the [NEMO configuration manager forum](https://forge.ipsl.jussieu.fr/nemo/discussion/forum/2).<br/>
5  If you don't find an answer in the archives, feel free to register and post your question.
6
7# How to Help
8   The development of SIREN highly depends on your input!<br/>
9   If you are trying SIREN let me know what you think of it (do you miss certain features?). Even if you decide not to use it, please let me know why.
10
11# How to report a bug
12   If you believe you have found a new bug, please report it.<br/>
13   Before submitting a new bug, first search through the database if the same bug has already been submitted by others
14
15   If you send only a (vague) description of a bug, you are usually not very
16   helpful and it will cost much more time to figure out what you mean. In
17   the worst-case your bug report may even be completely ignored.
18
19 <HR>
20   <b>
21   - @ref index
22   - @ref md_src_docsrc_1_install
23   - @ref md_src_docsrc_2_quickstart
24   - @ref md_src_docsrc_3_support_bug
25   - @ref md_src_docsrc_4_codingRules
26   - @ref md_src_docsrc_5_changeLog
27   - @ref todo
28   </b>
Note: See TracBrowser for help on using the repository browser.