On 4/27/07, Gwyn Evans <[EMAIL PROTECTED]> wrote:
Friday, April 27, 2007, 9:25:43 AM, you wrote:
> Could you please test if it works for you so that we can fix it
> for the release?
At this stage, I'd have thought that the only way it could get to be
part of the ongoing 1.3.0-incubating-beta1 (which is what I assume
you're referring to - it's unclear, but that's the only release I'm
aware of) is if we pulled that and restarted from scratch.
+1 with Gwyn. This can easily go into the next beta or the first RC.
This beta release is one in a series where we will move towards a
final 1.3.0. There is no doubt that this issue needs to be resolved
before we roll out 1.3.0, but we're not going to delay/pull the beta
release for any other issue than issues raised by the IPMC (i.e. legal
issues) or a critical undiscovered bug (security or blocking). Since
this fits neither case...
> I raised the priority to critical because I'd
> really like it to be part of the next train.
IMO, that's a /really/ bad idea - to me, any "Critical" issues would
be those that either break the system completely or have security
implications - in those cases, we might well be justified in pulling
any ongoing release or rushing out a 1.2.x release
Yep. Critical is only for deal breakers and "MUST FIX NOW OTHERWISE
WE'RE IN A WORLD OF HURT WE WILL LOOSE MILLIONS PEOPLE WILL DIE MY SSN
WILL BE AVAILABLE TO MILLIONS OF NIGERIAN 409 SCAMMERS OMG PONIES" and
any random number of exclamation marks inserted at random places.
Considering we're at WICKET-5xx and there have been at least 470
issues created in between, this doesn't list as critical to me.
Martijn
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.6 contains a very important fix. Download Wicket now!
http://wicketframework.org
