Henning Schmiedehausen wrote:
Hm,
I hate to spoil you here but according to a recent board discussion,
some discussion on [EMAIL PROTECTED] and a completely botched release
attempt in Velocity
My condolences to you...
land:
You actually have to roll and sign a tarball/zip ball on which the vote
happens. "Release-then-Vote" seems to be the only accepted way by the
board these days;
Thankfully, neither events in velocity-private nor board feelings apply here.
Either Jakarta PMC votes for it or receives an resolution, before that happens,
existing procedures [1] stay.
personally I do prefer "Vote-then-Release" myself but
that seems to be the way it is.
Agree. Doing otherwise is putting carriage before the horse. The closest I can
do to satisfy old ladies drinking tea is this "rc" trunk build [2]. Of course
those are not the files to be distributed: to get those, I actually would have
to do release first. And that would put me in catch 22 situation. Hence these RC
builds have to suffice.
On the release itself I'm +1, on the procedure I prefer to abstain. :-)
Thanks! Now need one more before starting tagging. Also I think I need to update
headers as per [3], is that correct?
Vadim
[1] http://jakarta.apache.org/commons/releases/release.html
[2] http://people.apache.org/~vgritsenko/regexp/
[3] http://www.apache.org/legal/src-headers.html
Best regards
Henning
On Tue, 2007-03-13 at 22:12 -0400, Vadim Gritsenko wrote:
Hi All,
With 5 recent bug fixes [1], one *major* speed improvement for {m,n} closures
[2], with other various optimizations to compiler and runtime, and with previous
release published sometime back in 2005 [3], now is the best, or at the very
least, really good time to to cut next, 1.5 release of the venerable Jakarta
Regexp package.
Please try out current svn (r517970) version [4] and test for any regressions,
and vote for a release. Regexp test suite can be run by issuing 'ant test' in
the checkout directory, and does not take even 3 seconds to complete.
Interactive testing can be done by using applet version [5].
The only known incompatibility with Regexp 1.4 is that pre-compiled RE programs
created with 'recompile' utility [6] for patterns containing reluctant closures
are not compatible with trunk. But, that should not be a problem since they did
not work correctly before anyway [7].
My vote for the release is +1.
Thanks,
Vadim
[1] http://jakarta.apache.org/regexp/changes.html
[2] http://issues.apache.org/bugzilla/show_bug.cgi?id=9153
[3] http://marc.info/?l=jakarta-regexp-dev&m=112429683615736
[4] http://svn.apache.org/repos/asf/jakarta/regexp/trunk/
[5] http://jakarta.apache.org/regexp/applet.html
[6]
http://svn.apache.org/repos/asf/jakarta/regexp/trunk/src/java/org/apache/regexp/recompile.java
[7] http://issues.apache.org/bugzilla/show_bug.cgi?id=27763
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
