Home My Page Projects Code Snippets Project Openings SML/NJ
Summary Activity Forums Tracker Lists Tasks Docs Surveys News SCM Files

SCM Repository

[smlnj] Diff of /pages/trunk/bugs/index.html
ViewVC logotype

Diff of /pages/trunk/bugs/index.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 3426, Wed Aug 5 18:13:52 2009 UTC revision 3427, Tue Aug 18 21:20:07 2009 UTC
# Line 18  Line 18 
18  <h3>Reporting Bugs</h3>  <h3>Reporting Bugs</h3>
19  There are currently two ways to report bugs to the SML/NJ developers:  There are currently two ways to report bugs to the SML/NJ developers:
20  by emailing a form, or by filling out a report using the  by emailing a form, or by filling out a report using the
21      <a href="http://www.cs.princeton.edu/%7Eappel/smlnj/bugform.cgi">      <a href="https://smlnj-gforge.cs.uchicago.edu/bugform.php">
22  online bug report form</a>.  online bug report form</a>.
23    
24  For email reports, the file <a href="bug-report-form">"bug-report-form"</a> contains a  For email reports, the file <a href="bug-report-form">"bug-report-form"</a> contains a
# Line 38  Line 38 
38  <li><a href="bug-report-form">bug-report-form</a>  <li><a href="bug-report-form">bug-report-form</a>
39  </menu>  </menu>
40    
41    <h3>Bug Tracker</h3>
42    
43    New bug reports are being kept in a <a href="http://smlnj-gforge.cs.uchicago.edu/tracker/?atid=215&group_id=33">
44    GForge issue tracker</a>.  The bug lists documented below still contain open
45    bugs prior to adoption of the new bug tracker (around the 110.70
46    timeframe and earlier).
47    
48  <h3>Bug Lists</h3>  <h3>Bug Lists</h3>
49  The SML/NJ bug reports are split into files with at most 200 bug  The SML/NJ bug reports are split into files with at most 200 bug
50  reports each, so that each file will be of a manageable size.  The  reports each, so that each file will be of a manageable size.  The
# Line 75  Line 82 
82  </menu>  </menu>
83    
84  <h3>Future of Bug Reporting</h3>  <h3>Future of Bug Reporting</h3>
85  With the next release we plan to switch to a new bug reporting method  
86  using the SourceForge bug management system.  Within one or two release cycles, we plan to review and migrate the
87    textual bug lists to our <a href="http://smlnj-gforge.cs.uchicago.edu/tracker/?atid=215&group_id=33">
88    GForge issue tracker</a>.
89    
90  <hr> Send your comments to <img src="../smlnj-list-logo.jpg" align=center><br>  <hr> Send your comments to <img src="../smlnj-list-logo.jpg" align=center><br>
91       <font size="-3">   Copyright &copy; 2003 The SML/NJ Fellowship.   <br>       <font size="-3">   Copyright &copy; 2003-9 The SML/NJ Fellowship.   <br>
92       </font>       </font>
93    
94  </blockquote>  </blockquote>

Legend:
Removed from v.3426  
changed lines
  Added in v.3427

root@smlnj-gforge.cs.uchicago.edu
ViewVC Help
Powered by ViewVC 1.0.0