README.git 2.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667
  1. This README applies to anyone who checks out the source from git.
  2. If you're reading this page on github.com, and you don't have git
  3. installed or know about git, you can download this repository by
  4. using the "download" button on github.com, right above the file
  5. list.
  6. PREAMBLE:
  7. ---------
  8. The git repository is structured in the expected way where "master" is the
  9. main branch you should use if you want to have bleeding-edge updates. Any
  10. other branch should be ignored since it will likely contain unstable
  11. and/or experimental developments.
  12. Generally speaking you should feel safe using the "master" branch in
  13. production code. Anything likely to break will be committed to another
  14. branch. Only bugfixes and clean non-breaking feature additions will be
  15. performed in master.
  16. All releases (post version 4.0.0) are tagged using the version number of
  17. that release. Earlier versions exist in a subversion repository at the
  18. old sourceforge project page.
  19. WHAT IS SWIFT MAILER?
  20. ---------------------
  21. Swift Mailer is a component based mailing solution for PHP 5.
  22. It is released under the MIT license.
  23. Homepage: http://swiftmailer.org/
  24. Documentation: http://swiftmailer.org/docs
  25. Mailing List: http://groups.google.com/group/swiftmailer
  26. Bugs: https://github.com/swiftmailer/swiftmailer/issues
  27. Repository: https://github.com/swiftmailer/swiftmailer
  28. Swift Mailer is highly object-oriented by design and lends itself
  29. to use in complex web application with a great deal of flexibility.
  30. For full details on usage, see the documentation.
  31. WHY SO MUCH CLUTTER?
  32. --------------------
  33. As you can probably see, there are a lot more files in here than you find in
  34. the pre-packaged versions. That's because I store notes (UML, RFCs etc) in
  35. the repository.
  36. The main library files live in /lib and the tests live in /tests. You can run
  37. the tests by pointing your web browser at /test-suite, or by running the
  38. command "php test-suite/run.php". Some tests will be "skipped" if
  39. tests/smoke.conf.php and tests/acceptance.conf.php are not editted. This is
  40. harmless and normal.
  41. If you want to create a bundled-up package from subversion you can do so if
  42. you have Ant (http://ant.apache.org/) installed. Simply run "ant package"
  43. from this directory and the tar.gz file will be created in the /build
  44. directory.
  45. Running the command "ant" with no arguments will bundle up the package without
  46. compressing it into a tar.gz file.
  47. Tests can also be run using "ant test" provided php is on your PATH
  48. environment variable.
  49. EoM