Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
Last revisionBoth sides next revision
bugzilla [2016/10/27 02:12] – created temabugzilla [2017/11/26 21:38] – hnv
Line 1: Line 1:
-====== The SaC-Zilla ======+====== Issue Tracking ======
  
-All reporting and management of errors in the SaC project is done via [[http://bugs.sac-home.org|SaC-Zilla]].+All reporting and management of errors in the SaC project is done via [[https://www.macs.hw.ac.uk/gitlab/sac-group/sac2c/issues|our issue tracker]] (//you will need to create an account for this//).
  
-===== Bug Submitting guidelines =====+===== Issue Submitting guidelines =====
  
 Although we are not exactly happy about receiving error reports, they form an important mechanism to improve the correctness and robustness of our tools. We will do our best to react on error reports as timely and accurately as possible. Although we are not exactly happy about receiving error reports, they form an important mechanism to improve the correctness and robustness of our tools. We will do our best to react on error reports as timely and accurately as possible.
Line 15: Line 15:
 In case your motivation to file a bug stems from the SAC compiler having generated a bug report for you, please follow these steps: In case your motivation to file a bug stems from the SAC compiler having generated a bug report for you, please follow these steps:
  
-  1. Copy and paste the leading comment in the autogenerated bug report into SaC-Zilla as plain text. +  -   Copy and paste the leading comment in the autogenerated bug report into SaC-Zilla as plain text. 
-  2. Submit the whole file with the autogenerated bug report as an attachment. +  -   Submit the whole file with the autogenerated bug report as an attachment. 
  
 If you are a member of the team, you must go the extra mile: try to make the failing program as small, concise, and independent as possible. If you are a member of the team, you must go the extra mile: try to make the failing program as small, concise, and independent as possible.
Line 27: Line 27:
 Note: the more accurate you describe the bug, the quicker the someone else will be able to fix the problem. Note: the more accurate you describe the bug, the quicker the someone else will be able to fix the problem.
  
-Also consult the [[http://bugs.sac-home.org/page.cgi?id=bug-writing.html|general error reporting guidelines]] in Sac-Zilla.+Also consult the [[https://www.macs.hw.ac.uk/gitlab/snippets/2|general error reporting guidelines]] in GitLab SaC project.