GitHub user dnwe opened a pull request:
https://github.com/apache/qpid-proton/pull/22
NO-JIRA: README improvements
* remove out-of-date product information from the README and include the
more
current information from the website
* add a new INSTALL file to contain the build and install instructions
from the existing README
* move all development and testing related info from that to the
DEVELOPERS file
* better explain how to run the various test suites and how they work
across proton-c and proton-j in the developers file
* other misc improvements across the contents of the files
* rename DEVELOPERS and INSTALL to have .md suffixes for better
rendering on GitHub
* add a symlink from README --> README.md for better landing page
rendering on GitHub
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/dnwe/qpid-proton improve-readmes
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/qpid-proton/pull/22.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #22
----
commit b532cf25756424c840047ad039b5c43eeb864046
Author: Dominic Evans <[email protected]>
Date: 2015-04-24T11:14:17Z
NO-JIRA: README improvements
* remove out-of-date product information from the README and include the
more
current information from the website
* add a new INSTALL file to contain the build and install instructions
from the existing README
* move all development and testing related info from that to the
DEVELOPERS file
* better explain how to run the various test suites and how they work
across proton-c and proton-j in the developers file
* other misc improvements across the contents of the files
* rename DEVELOPERS and INSTALL to have .md suffixes for better
rendering on GitHub
* add a symlink from README --> README.md for better landing page
rendering on GitHub
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
