source: public/content/contributing.shtml

Last change on this file was 14741, checked in by Mark Evenson, 10 years ago

html: change references from lisp.not.org to abcl.org and common-lisp.net as appropiate.

abcl.org names all permanent ABCL specific resources.

common-lisp.net replaces lisp.not.org as naming for non-ABCL specific
resources.

  • Property svn:eol-style set to LF
  • Property svn:keywords set to Id
File size: 2.4 KB
Line 
1<?xml version="1.0"?>
2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
3    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
4<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
5<head>
6  <title>Contributing: Armed Bear Common Lisp (ABCL) - Common Lisp on the JVM</title>
7  <link rel="stylesheet" type="text/css" href="style.css"/>
8  <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
9</head>
10
11<body>
12 <div class="header">
13   <h1>Contributing: Armed Bear Common Lisp (ABCL) - Common Lisp on the JVM</h1>
14 </div>
15
16<!--#include virtual="left-menu" -->
17
18<div style="margin-left:auto;margin-right:auto;width:20cm">
19
20
21
22
23
24
25
26  <h2>A quick guide to producing patches for ABCL</h2>
27
28This guide describes how to contribute patches to ABCL, while making
29sure that the patch doesn't introduce regressions.
30
31<ol>
32  <li> Build abcl and run the ansi-tests with the pristine tree before making patches
33    and store the test results. Invoke the following commands from the
34    abcl main directory:
35    <code>
36      <br/>ant abcl.clean
37      <br/>ant abcl.wrapper
38      <br/>ant test.ansi.interpreted
39      <br/>ant test.ansi.compiled
40    </code>
41    <br/>The test runs will report where their logs are written, keep those
42    files at hand for comparing them with later runs with modified code.
43  </li>
44  <li>
45    Develop your patch.
46  </li>
47  <li>
48    Build abcl and run the ansi-tests with your modification and store the test results.
49    The commands are as in the first step.
50  </li>
51  <li>
52    Compare the new test results with the pristine results, if there are no
53    additional failures, the patch should be ok. Example comparison for
54    linux would be
55    <code>
56    <br/>diff -u abcl-test-20093726-2037.log abcl-test-20094426-2044.log
57    </code>
58    <br/>Note that the file names are generated dynamically by the test runs.
59    The list of failed tests can be found at the end of the log, so that's
60    practically the only thing you're interested in. If the lists don't
61    differ, you've successfully created a patch with no ansi-test regressions.
62  </li>
63</ol>
64</div>
65<div style="float:left;width:100%">
66 <hr />
67 <p>Hosted as part of  <a href="http://common-lisp.net/">common-lisp.net</a>.</p>
68
69 <div class="check">
70   <a href="http://validator.w3.org/check/referer">Valid XHTML 1.0 Strict</a>
71 </div>
72<div style="float:right;font-size:10px;font-family:monospace">$Id: contributing.shtml 14741 2015-01-05 16:44:38Z mevenson $</div>
73</div>
74
75</body>
76</html>
Note: See TracBrowser for help on using the repository browser.