You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Robert Leland <rl...@apache.org> on 2003/08/17 05:43:41 UTC
[Validator - Draft Release Proposal] Release of Commons Validator
Validator Commons Committers I need your feedback.
Commons Validator has recently undergone refactoring with a few bugs
fixed and documentation updates. As of today the unit tests pass, and
known existing applications work correctly.
There are currently 3 outstanding Bugs reports
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20432
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20579
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22124
Bug 20432 - The original bug was fixed, and another user reported a
similar problem, but at a line number that looked unlikely.
Bug 20579 & 22124 Both deal with the Email validation.
After checking the RFC to verify that these Bug reports are valid.
I will add unit tests to cover these items so tests fail.
I propose that these bugs be addressed before the next release.
They must be marked either FIXED or INVALID.
For this Release I also propose we update the jar dependencies to be on the
latest Commons release namely:
commons-beanutils 1.6.1
commons-collections 2.1
commons-digester 1.5
commons-logging 1.0.3
oro 2.0.7
xml-apis 2.0.2 (Should we update this also ?)
JUnit 3.8.1
Additionally an updated set of release notes need to be generated.
I propose to use Ant to generate a changelog and use this as a basis
for the release notes.
Therefore I propose that when we release the tip of the main trunk in CVS
as that it be designated Commons Validator 1.1.0.
I am Volunteering as the release manager.
--
Robert Leland
------------------------------------------
Java, J2EE, Struts, Web Application Development
804 N. Kenmore Street +01-703-525-3580
Arlington VA 22201
Re: [Validator - Draft Release Proposal] Release of Commons Validator
Posted by Robert Leland <rl...@apache.org>.
David Graham wrote:
>--- Robert Leland <rl...@apache.org> wrote:
>
>
>>Validator Commons Committers I need your feedback.
>>
>>Commons Validator has recently undergone refactoring with a few bugs
>>fixed and documentation updates. As of today the unit tests pass, and
>>known existing applications work correctly.
>>
>>There are currently 3 outstanding Bugs reports
>>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20432
>>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20579
>>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22124
>>
>>Bug 20432 - The original bug was fixed, and another user reported a
>> similar problem, but at a line number that looked unlikely.
>>Bug 20579 & 22124 Both deal with the Email validation.
>> After checking the RFC to verify that these Bug reports are
>>valid.
>> I will add unit tests to cover these items so tests fail.
>>
>> I propose that these bugs be addressed before the next
>>release.
>> They must be marked either FIXED or INVALID.
>>
>>
>
>They can also be marked as LATER which I think is more appropriate. The
>tests fail now which means the email bugs are valid so they should be
>marked LATER and fixed for 1.1.1.
>
I would like to address them before the release.
Also now that the javascript validation functions are in Validator I
would like to unit test them also.
--
Robert Leland Robert@free2create.org
------------------------------------------
Java, J2EE, Struts, Web Application Development
804 N. Kenmore Street +01-703-525-3580
Arlington VA 22201
Re: [Validator - Draft Release Proposal] Release of Commons Validator
Posted by David Graham <gr...@yahoo.com>.
--- Robert Leland <rl...@apache.org> wrote:
> Validator Commons Committers I need your feedback.
>
> Commons Validator has recently undergone refactoring with a few bugs
> fixed and documentation updates. As of today the unit tests pass, and
> known existing applications work correctly.
>
> There are currently 3 outstanding Bugs reports
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20432
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20579
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22124
>
> Bug 20432 - The original bug was fixed, and another user reported a
> similar problem, but at a line number that looked unlikely.
> Bug 20579 & 22124 Both deal with the Email validation.
> After checking the RFC to verify that these Bug reports are
> valid.
> I will add unit tests to cover these items so tests fail.
>
> I propose that these bugs be addressed before the next
> release.
> They must be marked either FIXED or INVALID.
They can also be marked as LATER which I think is more appropriate. The
tests fail now which means the email bugs are valid so they should be
marked LATER and fixed for 1.1.1.
>
> For this Release I also propose we update the jar dependencies to be on
> the
> latest Commons release namely:
> commons-beanutils 1.6.1
> commons-collections 2.1
> commons-digester 1.5
> commons-logging 1.0.3
> oro 2.0.7
> xml-apis 2.0.2 (Should we update this also ?)
> JUnit 3.8.1
+1 as long as this doesn't conflict with Struts' dependencies as Struts is
currently the biggest user of Commons Validator.
>
> Additionally an updated set of release notes need to be generated.
> I propose to use Ant to generate a changelog and use this as a basis
> for the release notes.
+1
>
>
> Therefore I propose that when we release the tip of the main trunk in
> CVS
> as that it be designated Commons Validator 1.1.0.
> I am Volunteering as the release manager.
+1
Thanks Rob!
David
>
> --
> Robert Leland
> ------------------------------------------
> Java, J2EE, Struts, Web Application Development
>
> 804 N. Kenmore Street +01-703-525-3580
> Arlington VA 22201
>
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Re: [Validator - Draft Release Proposal] Release of Commons Validator
Posted by David Graham <gr...@yahoo.com>.
--- Robert Leland <rl...@apache.org> wrote:
> Validator Commons Committers I need your feedback.
>
> Commons Validator has recently undergone refactoring with a few bugs
> fixed and documentation updates. As of today the unit tests pass, and
> known existing applications work correctly.
>
> There are currently 3 outstanding Bugs reports
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20432
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20579
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22124
>
> Bug 20432 - The original bug was fixed, and another user reported a
> similar problem, but at a line number that looked unlikely.
> Bug 20579 & 22124 Both deal with the Email validation.
> After checking the RFC to verify that these Bug reports are
> valid.
> I will add unit tests to cover these items so tests fail.
>
> I propose that these bugs be addressed before the next
> release.
> They must be marked either FIXED or INVALID.
They can also be marked as LATER which I think is more appropriate. The
tests fail now which means the email bugs are valid so they should be
marked LATER and fixed for 1.1.1.
>
> For this Release I also propose we update the jar dependencies to be on
> the
> latest Commons release namely:
> commons-beanutils 1.6.1
> commons-collections 2.1
> commons-digester 1.5
> commons-logging 1.0.3
> oro 2.0.7
> xml-apis 2.0.2 (Should we update this also ?)
> JUnit 3.8.1
+1 as long as this doesn't conflict with Struts' dependencies as Struts is
currently the biggest user of Commons Validator.
>
> Additionally an updated set of release notes need to be generated.
> I propose to use Ant to generate a changelog and use this as a basis
> for the release notes.
+1
>
>
> Therefore I propose that when we release the tip of the main trunk in
> CVS
> as that it be designated Commons Validator 1.1.0.
> I am Volunteering as the release manager.
+1
Thanks Rob!
David
>
> --
> Robert Leland
> ------------------------------------------
> Java, J2EE, Struts, Web Application Development
>
> 804 N. Kenmore Street +01-703-525-3580
> Arlington VA 22201
>
>
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org