Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

No Format
TS-#### short summary (50 chars or less), not a sentence
Tested:
More Platform e.g. Ubuntu-9.0.4, OSX (10.5), FreeBSD (7.2), OpenSolaris (osol096)

More detailed explanatory text, if necessarydetailed explanatory text as necessary, patch attributions, and
what platforms the commit has been tested on.  Wrap it to about 72
characters or so.  In some contexts, the first line is treated as the
subject of an email and the rest of the text as the body.  The blank
line separating the summary from the body is critical (unless you omit
the body entirely); tools like rebase can get confused if you run the
two together.

...

  1. You are responsible for latest trunk to build and at least start up with your changes before you commit to SVN, on one of our supported platforms. This typically implies that you ought should to do an `svn up` to your tree and build before committing.
  2. Of course, we don't expect everyone to test on more than their preferred development platform(s), and we'll work with the Infraops team to increase our coverage with continuous integration tools and build-bots. At a minimum the the build should not break on the current primary buildbot slave which is http://ci.apache.org/buildslaves/bb-vm_ubuntuImage Removed (Ubuntu Linux). If the primary build bot is broken, it is the commiter's responsibility to get the build working or find someone to help them.
  3. If the trunk is broken, i.e. it doesn't build and/or run even without your changes, please don't commit! Meaning, please don't pour No more fuel on the fire please.
  4. If your changes result in a non-functioning Traffic Server (e.g. start fails, simple forward proxy browsing is broken, etc) please consider backing out your changes and submitting the changes for review under a new TS Jira ticket and asking for reviewers.
  5. If your changes are so large that you want to make partial commits, create a SVN branch or work on a local repository using a version control system like Git or Mercurial. Several of the developers in the community use Git and hg, and can provide help and tips on how to use it.

...