[Practicalxml-commits] SF.net SVN: practicalxml:[72] trunk/README.txt

[Auto-Generated S. C. M. <pra...@li...>]

Revision: 72
          http://practicalxml.svn.sourceforge.net/practicalxml/?rev=72&view=rev
Author:   kdgregory
Date:     2009-01-14 13:37:46 +0000 (Wed, 14 Jan 2009)

Log Message:
-----------
add README

Added Paths:
-----------
    trunk/README.txt

Added: trunk/README.txt
===================================================================
--- trunk/README.txt	                        (rev 0)
+++ trunk/README.txt	2009-01-14 13:37:46 UTC (rev 72)
@@ -0,0 +1,48 @@
+Practical XML - Providing What The JDK Doesn't
+
+    This library is designed to be an easy-to-use wrapper around the XML
+    support built-in to the JDK. It is based on the idea that the JDK
+    implementations will live forever and be regularly updated, something
+    that cannot be said about third-party alternatives.
+
+Licensing and Copyright
+
+    This library is released under the Apache 2 license:
+    http://www.apache.org/licenses/LICENSE-2.0
+
+    Copyright is retained by the individual maintainers, for the code
+    that they have contributed. In the case of patch submissions from
+    third parties, the patch contributor implicitly assigns copyright
+    to the maintainer who implements the patch.
+
+Release Numbering
+
+    All builds post initial release have a three part revision number:
+    MAJOR.MINOR.PATCH
+
+        MAJOR releases are not required to be backwards compatible with
+              the previous such release. For example, the 1.0.0 release
+              has a different package structure than the 0.9.0 release.
+              It is intended that there will never be a change to the
+              major release number, although "never" is a long time.
+        MINOR releases will happen whenever a maintainer decides that
+              one is needed, typically driven by significant new
+              functionality and a desire to have the release in a central
+              repository. Minor releases preserve backwards compatibility:
+              code written for one minor release will work when linked
+              with another minor release.
+        PATCH releases won't actually get released: the PATCH revision
+              number should be incremented with each checkin, in preference
+              to using a "-SNAPSHOT" of the next minor release. This will
+              lock users into keeping their build scripts and local repository
+              up-to-date, which is a Good Thing.
+
+    Major and minor releases will be tagged in the Subversion repository,
+    using the form "rel-X.Y", where X and Y are the major and minor release
+    numbers. Patch releases may be tagged using the form "rel-X.Y.Z", if the
+    maintainer decides that it's important to rebuild that particular release
+    (although making it a minor release might be a better idea).
+
+    Major and minor releases will be available for download from Sourceforge
+    ( http://sourceforge.net/project/showfiles.php?group_id=234884 ), and also
+    from the Central Maven Repository.


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.