Looks good to me. I'll add these and recreate the release tonight.
Mike
On May 17, 2004, at 7:54 AM, Kalnichevski, Oleg wrote:
Grrrrrrr.....
This time inline -------------------------------------------------------------------
Index: news.xml =================================================================== RCS file: /home/cvspublic/jakarta-commons/httpclient/xdocs/news.xml,v retrieving revision 1.26 diff -u -r1.26 news.xml --- news.xml 17 May 2004 03:46:44 -0000 1.26 +++ news.xml 17 May 2004 11:33:41 -0000 @@ -12,9 +12,39 @@ <body>
<section name="17 May 2004 - HttpClient 3.0 alpha1 released">
- <p>We are pleased to announce the first HttpClient 3.0 release. This release contains quite a
- number of additions and enhancements. Please <a href="downloads.html">download</a> and
- let us know what you think.</p>
+ <p>We are pleased to announce the first HttpClient 3.0 release.
+ HttpClient 3.0 provides a wealth of features and enhancements
+ that did not make it into the 2.0 release while preserving API
+ compatibility as much as possible. In a relatively few case
+ <a href="API_CHANGES_3_0.txt">API compatibility with HttpClient
+ 2.0</a> could not maintained.
+ </p>
+ <p>
+ Most noteworthy enhancements include:
+ <ul>
+ <li>New preference architecture</li>
+ <li>Improved exception handling framework</li>
+ <li>Granular non-standards configuration and tracking</li>
+ <li>Improved authentication framework</li>
+ <li>Plug-in mechanism for authentication modules</li>
+ <li>Cookie specification plug-in mechanism</li>
+ <li>Cross-site redirect support</li>
+ </ul>
+ </p>
+ <p>
+ We see our fellow Apache developers as well as other open-source
+ projects already reliant on HttpClient as the primary target
+ audience for this release. This can be the right moment to evaluate
+ HttpClient 3.0 and give us some feedback, critique or thoughts on
+ the new API and file requests for additional features. The goal of
+ the second ALPHA release is to incorporate the feedback, polish the
+ API and update documentation. The next ALPHA release will target the
+ wider audience beyond the Apache Jakarta and Apache WS communities.
+ </p>
+ <p>
+ Please <a href="downloads.html">download</a> and
+ let us know what you think.
+ </p>
</section>
<section name="16 April 2004 - Welcome Jakarta HttpClient!">
Index: status.xml
===================================================================
RCS file: /home/cvspublic/jakarta-commons/httpclient/xdocs/status.xml,v
retrieving revision 1.23
diff -u -r1.23 status.xml
--- status.xml 17 May 2004 03:46:44 -0000 1.23
+++ status.xml 17 May 2004 11:33:41 -0000
@@ -18,13 +18,29 @@
A number of major changes have already been incorporated into the 3.0 code base, though
there is still room for more in the final release. We would like to encourage
comment on the API changes and additions made so far.</p>
-
+ <p>
+ Most noteworthy enhancements include:
+ <ul>
+ <li>New preference architecture</li>
+ <li>Improved exception handling framework</li>
+ <li>Granular non-standards configuration and tracking</li>
+ <li>Improved authentication framework</li>
+ <li>Plug-in mechanism for authentication modules</li>
+ <li>Cookie specification plug-in mechanism</li>
+ <li>Cross-site redirect support</li>
+ </ul>
+ </p>
<p>HttpClient 2.0 is no longer being actively developed, with the exception of
bug fixes. A 2.0.1 release is planned for the near future.</p>
<p>It is important to note that HttpClient CVS HEAD is no longer fully compatible
with 2.0 APIs. We encourage using the <tt>HTTPCLIENT_2_0_BRANCH</tt> for production
- development until the 3.0 APIs are stabilized.</p>
+ development until the 3.0 APIs are stabilized. API incompatibilities with HttpClient
+ 2.0 are described <a href="API_CHANGES_3_0.txt">here</a>.
+ </p>
+ <p>Bug reports targeted for the next release can be found
+ <a href="http://nagoya.apache.org/bugzilla/buglist.cgi? bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED& email1=&emailtype1=substring&emailassigned_to1=1& email2=&emailtype2=substring&emailreporter2=1& bugidtype=include&bug_id=&changedin=&votes=& chfieldfrom=&chfieldto=Now&chfieldvalue=& product=Commons&component=HttpClient& target_milestone=3.0+Alpha+2&short_desc=& short_desc_type=allwordssubstr&long_desc=& long_desc_type=allwordssubstr&bug_file_loc=& bug_file_loc_type=allwordssubstr&keywords=& keywords_type=anywords&field0-0-0=noop&type0-0-0=noop& value0-0-0=&cmdtype=doit&newqueryname=& order=Reuse+same+sort+as+last+time">here</a>.
+ </p>
</section>
<section name="Release Info">
-------------------------------------------------------------------
-----Original Message----- From: Kalnichevski, Oleg Sent: Monday, May 17, 2004 13:47 To: Commons HttpClient Project Subject: RE: 3.0 alpha1 build [PATCH] status & news
Mike,
I feel we need a little stronger and more focused sales pitch. This is going to be a very important release for all of us and our message must be loud and clear with regards to what this release is intended to be and what its intended target is. If we fail to generate enough interest in the coming two to three months, we increase the risk of finding ourselves in an unpleasant situation with too many people expressing unhappiness with the new API after the official API freeze.
Here's my attempt at extending status & news pages. Feel free to make any modifications you deem necessary.
Oleg
-----Original Message----- From: Michael Becke [mailto:[EMAIL PROTECTED] Sent: Monday, May 17, 2004 6:11 To: Commons HttpClient Project Subject: 3.0 alpha1 build
I've uploaded the 3.0 alpha1 build to my apache account
<http://www.apache.org/~mbecke/httpclient-3.0-alpha1/>. Please have a
look and let me know if I've missed anything. This release was created
with JDK1.3.1 since it seems that Maven RC2 does not work with 1.2.2.
I don't think this will cause any issues, but if anyone is using 1.2.2
please give it a shot. This is also the first time I've signed a
release. My public key is in the KEYS file so please try that out as
well.
My plan is to finish this off tomorrow night and post the release. I
was thinking of leaving the 2.0 docs as the main HttpClient page, and
just adding a link to the 3.0 version in another directory.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
*********************************************************************** ****************************
The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
*********************************************************************** ****************************
*********************************************************************** ****************************
The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system.
*********************************************************************** ****************************
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
