commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Don Brown <donald.br...@gmail.com>
Subject Re: [VOTE] Release Commons Validator 1.2.0 RC1
Date Tue, 11 Oct 2005 01:01:30 GMT
Nope, not at all. I'll roll it tomorrow afternoon, so do you worst until
then :)

Don

On 10/10/05, Niall Pemberton <niall.pemberton@blueyonder.co.uk> wrote:
>
> Don,
>
> As we're going to have a rc2 - I thought I would put in the maven 2
> changes:
>
> http://svn.apache.org/viewcvs.cgi?rev=312771&view=rev
>
> The same as were requested for BeanUtils...
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=37011
>
> Hopefully you haven't started on rc2 and I haven't messed anything up.
>
> Niall
>
> ----- Original Message -----
> From: "Don Brown" <donald.brown@gmail.com>
> Sent: Monday, October 10, 2005 9:07 PM
>
>
> As I understand it, if the vote doesn't succeed, then we ignore it, and
> roll
> rc2.
>
> On 10/10/05, Niall Pemberton <niall.pemberton@blueyonder.co.uk> wrote:
> >
> > Don,
> >
> > First, thanks for doing this. I have a few comments:
> >
> > * xdocs/changes.xml - the change log needs updating to RC1 (with the
> date)
>
> * xdocs/download.xml - we should include rc1 under the "development
> > releases" on the download page
>
>
> Darn. I'll fix those and roll a rc2.
>
> * JDK Version - The jar indicates it was built with JDK 1.4 - for the same
> > reasons as here....
> >
> > http://www.mail-archive.com/commons-dev@jakarta.apache.org/msg66582.html
> >
> > ....I would we prefer it was built with JDK 1.3 - even if there are no
> > issues with running it on JDK 1.3, I think it will make users feel more
> > secure to see JDK 1.3 in the jar's manifest, rather than 1.4
>
>
> Hmm...the compiler is set to compile code that works with 1.3 so
> technically
> that shouldn't be a problem. Still, I'll install 1.3 and compile rc2 with
> it.
>
> Also, not quite sure about voting on a RC1 - don't we just need to make it
> > available and announce it (as you have done) and then once its been out
> > there a while (1/2 weeks?) then call for a vote (assuming no issues
> arise)
> > on whether to cut a 1.2.0 release based on RC1?
> >
> > Also, I would upload the web site to the proper place - that way anyone
> > going to the download page will see rc1 there available as a
> "development
> > release".
>
>
> As I understand it, the release has to succeed before I make it available.
> Therefore, rc1 will only exist in subversion as a tag, but hopefully I'll
> get rc2 right and it'll go public.
>
> Don
>
> Niall
> >
> > ----- Original Message -----
> > From: "Don Brown" <donald.brown@gmail.com>
> > Sent: Monday, October 10, 2005 6:48 PM
> >
> >
> > I believe commons-validator is ready to start the journey to 1.2.0final..
> > All the open tickets are
> > enhancements.
> >
> > See the zips at:
> > http://people.apache.org/~mrdon/commons-validator/1.2.0-rc1
> >
> > See the website at:
> >
> >
>
> http://people.apache.org/~mrdon/commons-validator/1.2.0-rc1/site/index.html
> >
> >
> > ------------------------------ --------------------------
> > [ ] +1 Release commons-validator-1.2.0-rc1
> > [ ] +0 not too fussed, but OK
> > [ ] -0 won't block, but think imperfect
> > [ ] -1 not until xxx is fixed
> > --------------------------------------------------------
> >
> > Don
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message