commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <>
Subject Re: [VOTE] Release Validator 1.2.0
Date Mon, 14 Nov 2005 03:55:59 GMT
Stephen, thanks for all your feedback.

I had created a page on the Wiki which provided a summary of the main
changes in Validator 1.2.0 - unfortunately it didn't include anything on the
dependency changes. I have now added an entry in the "Changes Report" for
the dependency changes in Validator 1.2.0. I have also included a section in
the Release Notes on the wiki. The Validator "home" page and "Downloads"
pages both point to the "Changes Report" and the Wiki "Release Notes" page.

Thanks for pointing out the Commons IO example - I have also changed the
Validator site to include the suggestions you make:

The home page now includes release, javadoc and support information.
The "Source Repository" page has been improved (as per commons io)
The "Issue Tracking" page has been added (as per commons io)

I have also added multiple copies of the javadocs on the server

Since the changes are only documentation, I propose we proceed with the vote
based on RC3 (rather than rolling a new release candidate).

Thanks again.


P.S. When I copied the cvs-usage.xml from Commons IO I noticed in the Apache
License section had "iouage" rather than "language" - looks like someone
copied the docs from Commons Lang and did a global change from "lang" to
"io" - other files seem to be similarly affected.

----- Original Message ----- 
From: "Stephen Colebourne" <>
Sent: Sunday, November 13, 2005 5:30 PM

> My main comment is that it took a while to figure out how the
> collections classes were being picked up (from beanutils). This should
> defnitely be in the release notes (which I would prefer being a little
> larger).
> So, -0 for now, +1 once the release notes state something about the
> removal of collections dependency via beanutils (preferably adding real
> release notes in text format)
> For the future we could improve a couple of maven generated website
> pages as per commons-io:
> and add documentation, release and support sections to the home page, eg:
> (at present, the download link is only in the left margin)
> Also, you may want to consider having multiple copies of the javadocs on
> the server, eg:
> (link)
> Stephen

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message