Permalink
Browse files

removed development information and put it in the wiki

git-svn-id: https://svn.apache.org/repos/asf/incubator/couchdb/trunk@667966 13f79535-47bb-0310-9956-ffa450edef68
  • Loading branch information...
1 parent be20702 commit ff10e0786f4b09c8afe5fb13d2795583ea445ef5 @nslater nslater committed Jun 15, 2008
Showing with 0 additions and 45 deletions.
  1. +0 −45 README
View
@@ -242,51 +242,6 @@ your system wide `/Library/LaunchDaemons` directory.
Windows documentation is incomplete. Please submit suggestions.
-Development
------------
-
-### Reconfiguring the Build System ###
-
-If you have edited any of the files used by the build system, such as the
-`Makefile.am` files, you will need to reconfigure your source.
-
-To reconfigure the source run the following command from the root directory:
-
- autoreconf && ./confgure
-
-### Checking In Changes ###
-
-If your source directory has been configured or built you will need to clean
-the generated files before checking into the repository by running the
-following command:
-
- make local-clean
-
-If everything was successful you should now have a pristine checkout.
-
-### Making a Release ###
-
-The following steps should be taken prior to preparing the release:
-
- svn cp trunk branches/Y.Y.x
- svn cp branches/Y.Y.x tags/Y.Y.Y
- svn export tags/Y.Y.Y export
-
-You must then use the `export` directory to prepare the release.
-
-To build the source for distribution you should then run the following command:
-
- ./configure && make distcheck
-
-If everything was successful you should see an appropriately named `tar.gz` file
-sitting in the root directory ready for distribution.
-
-### Release Checklist ###
-
- 1. Update the `README` file with important information.
- 2. Update the `NEWS` file with change information.
- 3. Update the `acinclude.m4` file with version information.
-
[01]: http://www.gnu.org/software/automake/
[02]: http://www.gnu.org/software/autoconf/
[03]: http://www.gnu.org/software/libtool/

0 comments on commit ff10e07

Please sign in to comment.