olegk 2003/07/26 08:09:27
Modified: httpclient/xdocs downloads.xml news.xml releases.xml
status.xml
Log:
2.0 Release Candidate 1 documentation & site update
Contributed by Oleg Kalnichevski
Revision Changes Path
1.20 +6 -4 jakarta-commons/httpclient/xdocs/downloads.xml
Index: downloads.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/downloads.xml,v
retrieving revision 1.19
retrieving revision 1.20
diff -u -r1.19 -r1.20
--- downloads.xml 2 Jul 2003 01:28:50 -0000 1.19
+++ downloads.xml 26 Jul 2003 15:09:27 -0000 1.20
@@ -17,16 +17,18 @@
</p>
<ul>
<li><a href="http://jakarta.apache.org/builds/jakarta-commons/release/commons-httpclient/v2.0/">
- Release 2.0 Beta 2</a> - 2 June 2003</li>
+ Release 2.0 Release Candidate 1</a> - 28 July 2003</li>
</ul>
<p>
Nightly source drops can be obtained
<a href="http://jakarta.apache.org/builds/jakarta-commons/nightly/commons-httpclient/">here</a>.
+ Please note that nightly drops may no longer be 2.0 API compatible.
</p>
<p>
The latest <a href="http://jakarta.apache.org/gump/">Gump</a> generated
binary
can be obtained <a href="http://gump.covalent.net/jars/latest/jakarta-commons/">here</a>.
- </p>
+ Please note that nightly drops may no longer be 2.0 API compatible.
+ </p>
<p>
The CVS repository for <em>HttpClient</em> can be
<a href="http://cvs.apache.org/viewcvs/jakarta-commons/httpclient/">browsed
online</a>.
@@ -36,7 +38,7 @@
<a href="http://jakarta.apache.org/site/cvsindex.html">CVS server</a>.
</p>
<p>
- If you are using Maven for your project, you can create a dependancy in your
+ If you are using Maven for your project, you can create a dependency in your
project.xml with the following block:
<pre>
<dependency>
1.21 +9 -1 jakarta-commons/httpclient/xdocs/news.xml
Index: news.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/news.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- news.xml 2 Jul 2003 01:28:50 -0000 1.20
+++ news.xml 26 Jul 2003 15:09:27 -0000 1.21
@@ -11,6 +11,14 @@
<body>
+ <section name="28 July 2003 - HttpClient 2.0 Release Candidate 1 released">
+ <p>With this release the <em>HttpClient 2.0 BETA</em> development
phase has been
+ concluded. The number of bugs discovered in the course of the BETA development
+ has been surprisingly low. We are growing confident that <em>HttpClient
+ 2.0</em> has reached the required level of maturity, and we hope to have
a final 2.0
+ release by the end of the Summer or the mid Autumn the latest.</p>
+ </section>
+
<section name="02 July 2003 - HttpClient 2.0 Beta 2 released">
<p>This release contains some minor bug fixes and documentation enhancements.
Most likely this will be the final beta release before 2.0 Release Candidate 1. As
1.13 +6 -6 jakarta-commons/httpclient/xdocs/releases.xml
Index: releases.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/releases.xml,v
retrieving revision 1.12
retrieving revision 1.13
diff -u -r1.12 -r1.13
--- releases.xml 2 Jul 2003 01:28:50 -0000 1.12
+++ releases.xml 26 Jul 2003 15:09:27 -0000 1.13
@@ -43,6 +43,11 @@
<li>Check out and thoroughly test the package code that you plan to
release.<br/><br/></li>
+ <li>Update release_notes.txt. This file should be updated in CVS when
+ patches are committed, but it is frequently not. Be sure all relevant
+ changes since the last release are included. This file should be published
+ along with the release source and binary distributions.<br/><br/></li>
+
<li>Update the project version number in the <code>build.xml</code>,
<code>project.xml</code>, <code>status.xml</code>, <code>downloads.xml</code>,
and the HttpMethodBase useragent string. There is an Ant property named
@@ -63,11 +68,6 @@
to do the build, 1.2.2. Review the generated documentation
to ensure that it correctly reflects the functionality (and the
version number) of this code.<br/><br/></li>
-
- <li>Update release_notes.txt. This file should be updated in CVS when
- patches are committed, but it is frequently not. Be sure all relevant
- changes since the last release are included. This file should be published
- along with the release source and binary distributions.<br/><br/></li>
<li>Create a news item. This should be added to httpclient/xdocs/news.xml
and
the jakarta-site2/xdocs/site/news.xml as well as a one liner in
1.21 +26 -10 jakarta-commons/httpclient/xdocs/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/httpclient/xdocs/status.xml,v
retrieving revision 1.20
retrieving revision 1.21
diff -u -r1.20 -r1.21
--- status.xml 2 Jul 2003 01:28:50 -0000 1.20
+++ status.xml 26 Jul 2003 15:09:27 -0000 1.21
@@ -14,21 +14,37 @@
<body>
<section name="Current Status">
- <p>For all current committers and anyone wishing to contribute to or use
- <em>HttpClient</em>, we are now in the final stages of 2.0 development.</p>
+ <p>HttpClient development team to pleased to announce that <em>HttpClient
2.0 BETA</em>
+ development phase has been concluded. The number of bugs discovered in the course
of the
+ BETA development has been surprisingly low. We are growing confident that <em>HttpClient
+ 2.0</em> has reached the required level of maturity, and we hope to have
a final 2.0
+ release by the end of the Summer or the mid Autumn the latest.</p>
- <p>Only bug fixes and documentation enhancements will be made to the 2.0
- code base in the next few weeks. We hope to have a final 2.0 release shortly.</p>
+ <p>Only critical or major bug fixes and javadocs enhancements will be made to the
2.0
+ code base in the next few weeks.</p>
- <p>Now that 2.0 beta 2 has been released initial development for post 2.0 releases
- can begin. A CVS branch of the 2.0 code will be made shortly so that 2.1 development
- can begin on the HEAD.</p>
+ <p>Meanwhile, the HttpClient development team has been busy working on the next
version
+ of <em>HttpClient</em>. The next version of HttpClient is going to
build upon the
+ foundation laid with <em>HttpClient 2.0</em> while addressing those
architectural
+ shortcomings and flaws identified in the course of 2.0 development. Several well
known
+ and much complained about problems cannot be resolved while maintaining complete
2.0 API
+ compatibility. The primary objective of the next version is to fix those design
limitations,
+ breaking 2.0 API compatibility where absolutely unavoidable, while preserving overall
+ compatibility with 2.0 use patterns.</p>
+
+ <p>Depending upon how drastic those API changes are going to be, the next version
of
+ HttpClient will be designated as <tt>2.1</tt>, <tt>2.5</tt>
or <tt>3.0</tt>.
+ The decision is to be taken before 2.0 final release.</p>
+
+ <p>It is important to note that HttpClient CVS HEAD may (and already is) no longer
be
+ compatible with 2.0 APIs. We strongly encourage to use <tt>HTTPCLIENT_2_0_BRANCH</tt>
+ until next version API are stabilized.</p>
</section>
<section name="Release Info">
<p>Current Release: <a href="http://jakarta.apache.org/builds/jakarta-commons/release/commons-httpclient/v2.0/">
- Release 2.0 Beta 2</a></p>
- <p>Planned Next Release: 2.0 Release Candidate 1</p>
+ Release 2.0 Release Candidate 1</a></p>
+ <p>Planned Next Release: 2.0 Release Candidate 2</p>
</section>
</body>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
|