You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Niall Pemberton <ni...@blueyonder.co.uk> on 2006/03/17 00:04:41 UTC
[VOTE] Release Validator 1.2.1 based on RC2
I have just uploaded release candidate 2 (RC2) for Commons Validator 1.2.1.
The only differences from RC1 has been to remove the dependency on
commons-build and bring the ant script more into line with the maven build.
RC2 is here:
http://people.apache.org/~niallp/commons-validator-rc2/
Site here:
http://people.apache.org/~niallp/commons-validator-rc2/site/
Release notes here:
http://people.apache.org/~niallp/commons-validator-rc2/site/changes-report.html
------------
[ ] +1 I support this release
[ ] +0
[ ] -0
[ ] -1 I do not support this release because...
------------
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE] Release Validator 1.2.1 based on RC2
Posted by Niall Pemberton <ni...@gmail.com>.
This is vote and the release of Validator 1.2.1 is CANCELLED.
Following feeback the version number is being bumped up to 1.3.0. I'll
post a new vote once a RC for 1.3.0 has been built.
Niall
On 3/16/06, Niall Pemberton <ni...@blueyonder.co.uk> wrote:
> I have just uploaded release candidate 2 (RC2) for Commons Validator 1.2.1.
> The only differences from RC1 has been to remove the dependency on
> commons-build and bring the ant script more into line with the maven build.
>
> RC2 is here:
> http://people.apache.org/~niallp/commons-validator-rc2/
>
> Site here:
> http://people.apache.org/~niallp/commons-validator-rc2/site/
>
> Release notes here:
> http://people.apache.org/~niallp/commons-validator-rc2/site/changes-report.html
>
> ------------
> [ ] +1 I support this release
> [ ] +0
> [ ] -0
> [ ] -1 I do not support this release because...
> ------------
>
> Niall
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [validator] Comments on Validator 1.2.1 based on RC2
Posted by Niall Pemberton <ni...@gmail.com>.
On 3/17/06, Stephen Colebourne <sc...@btopenworld.com> wrote:
> --- Niall Pemberton <ni...@gmail.com> wrote:
> > > - Issue tracking page - link to create a new bug
> > sets an invalid version
> >
> > I tried it an it sets a version of "unspecified" -
> > thats a valid
> > version and IMO is the correct thing to do. Tells us
> > that the user just took the default.
> My expectation was that it would highlight v1.3 as
> that is the version the bug is reported against, but
> its not something I'm blocking on.
I don't think we can assume this is the case. In Struts we currently
have 5 "GA" releases and we still get questions on all of them
(notmuch on 1.0, but it still happens) and we have different versions
of Validator out being used in those Struts versions. At this point
its more likely someone will be using Validator 1.1.3, 1.1.4 or 1.2.0.
Until a "GA" quality release of Struts with Validator 1.3.0 happens I
think it is likely to remain so.
> > > - Left navigation javadoc link should point at
> > api-release
> >
> > The docs are distributed locally - so in a released
> > distro this will
> > point to the local "released" copy. When browsing
> > online the latest.
> > I'll add a new "javadocs" menu with the released
> > versions clearly marked.
> I would have kept the SVN latest docs in the
> development menu (as it should only be used by
> advanced 'developer' users). Also, I would have named
> it Javadocs not JavaDocs as it looks nicer :-) Hardly
> release breakers though.
OK I'll change Javadoc to JavaDoc. Not worth a new RC though.
> > > - Left navigation svn javadoc link should be
> > relative to avoid external link
> >
> > I want it to not be relative - that way the link in
> > the local copy
> > distributed with the distro will work and not be
> > "broken".
> I don't think this is correct, as the apidocs folder
> is in the release. Unless you want to actually connect
> to the true latest docs, in which case the http link
> is needed.
Yes I want them to point to the true latest docs.
Niall
> Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [validator] Comments on Validator 1.2.1 based on RC2
Posted by Stephen Colebourne <sc...@btopenworld.com>.
--- Niall Pemberton <ni...@gmail.com> wrote:
> > - Issue tracking page - link to create a new bug
> sets an invalid version
>
> I tried it an it sets a version of "unspecified" -
> thats a valid
> version and IMO is the correct thing to do. Tells us
> that the user just took the default.
My expectation was that it would highlight v1.3 as
that is the version the bug is reported against, but
its not something I'm blocking on.
> > - Left navigation javadoc link should point at
> api-release
>
> The docs are distributed locally - so in a released
> distro this will
> point to the local "released" copy. When browsing
> online the latest.
> I'll add a new "javadocs" menu with the released
> versions clearly marked.
I would have kept the SVN latest docs in the
development menu (as it should only be used by
advanced 'developer' users). Also, I would have named
it Javadocs not JavaDocs as it looks nicer :-) Hardly
release breakers though.
> > - Left navigation svn javadoc link should be
> relative to avoid external link
>
> I want it to not be relative - that way the link in
> the local copy
> distributed with the distro will work and not be
> "broken".
I don't think this is correct, as the apidocs folder
is in the release. Unless you want to actually connect
to the true latest docs, in which case the http link
is needed.
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE] Release Validator 1.2.1 based on RC2
Posted by Niall Pemberton <ni...@gmail.com>.
On 3/16/06, Stephen Colebourne <sc...@btopenworld.com> wrote:
> Niall Pemberton wrote:
> > ------------
> > [ ] +1 I support this release
> > [ ] +0
> > [X] -0
> > [ ] -1 I do not support this release because...
> > ------------
>
> - The addition of the routines package should either be documented as
> not available for general use until v1.3, or the whole release should be
> v1.3. IMHO, such a major refactoring is unacceptable in a minor point
> release. (Hence -0)
I thought my reply earlier had satisfied you on this. Anyway, I'll
bump the version number up to 1.3.0 then.
> - MD5 didn't work for me, but I have a very dubious checker so don't put
> too much credence on that.
>
> - src distro doesn't unzip to a directory name ending with -src
> (optional change)
>
> Site issues:
> - Issue tracking page - link to create a new bug sets an invalid version
I tried it an it sets a version of "unspecified" - thats a valid
version and IMO is the correct thing to do. Tells us that the user
just took the default.
> - The Jakarta logo (top left) is different to most other commons sites,
> and causes the header images to clash and make the header double height
> when viewed at smaller browser widths
OK I'll change this.
> - The left navigation legend has been turned off
OK. I'll turn it back on.
> - Left navigation javadoc link should point at api-release
The docs are distributed locally - so in a released distro this will
point to the local "released" copy. When browsing online the latest.
I'll add a new "javadocs" menu with the released versions clearly
marked.
> - Left navigation svn javadoc link should be relative to avoid external link
I want it to not be relative - that way the link in the local copy
distributed with the distro will work and not be "broken".
> Stephen
> PS. I was trying to get to check out the RC before the vote, I just
> never got to it :-(
Hey, thanks for the feedback - its appreciated at whatever point in
the process :-)
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE] Release Validator 1.2.1 based on RC2
Posted by Stephen Colebourne <sc...@btopenworld.com>.
Niall Pemberton wrote:
> ------------
> [ ] +1 I support this release
> [ ] +0
> [X] -0
> [ ] -1 I do not support this release because...
> ------------
- The addition of the routines package should either be documented as
not available for general use until v1.3, or the whole release should be
v1.3. IMHO, such a major refactoring is unacceptable in a minor point
release. (Hence -0)
- MD5 didn't work for me, but I have a very dubious checker so don't put
too much credence on that.
- src distro doesn't unzip to a directory name ending with -src
(optional change)
Site issues:
- Issue tracking page - link to create a new bug sets an invalid version
- The Jakarta logo (top left) is different to most other commons sites,
and causes the header images to clash and make the header double height
when viewed at smaller browser widths
- The left navigation legend has been turned off
- Left navigation javadoc link should point at api-release
- Left navigation svn javadoc link should be relative to avoid external link
Stephen
PS. I was trying to get to check out the RC before the vote, I just
never got to it :-(
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org