Mailing-List: contact tapestry-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tapestry development" <tapestry-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of glongman@gmail.com designates
 64.233.170.194 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=l+tSKotyTzfKQklwGoSaY+cDcyteKhxfy2tQEheAN0XZBgNu6hC6PhOFz9NnUSnx9y7OiCtL2r5xHqyoYxqaZzuUB3QfQS5mxOqwGLksVnBS/JMTDyZ4Y4NcOeeekMEEqzvhCJ4V6XxAWSZF/KOZYrHtrObWZeGxn3gJ+oUQtvk=
Message-ID: <94b38848050318175850eaafe8@mail.gmail.com>
Date: Fri, 18 Mar 2005 19:58:16 -0600
From: Geoff Longman <glongman@gmail.com>
Reply-To: Geoff Longman <glongman@gmail.com>
To: Tapestry development <tapestry-dev@jakarta.apache.org>
Subject: Re: [VOTE] Release 3.0.3
In-Reply-To: <2d585f3e1525d4ea3776cd17b62070dd@ehatchersolutions.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
References: <423B7DF0.5070309@columbia.edu>
	 <2d585f3e1525d4ea3776cd17b62070dd@ehatchersolutions.com>

I think the interface change your spotted Erik is
IEngine.getResourceChecksumSource().

Isn't that the backport of Howards fix for the asset security hole?

Geoff


On Fri, 18 Mar 2005 20:45:11 -0500, Erik Hatcher
<erik@ehatchersolutions.com> wrote:
> Paul,
> 
> First - kudos for picking up the ball on this one.  I strongly believe
> keeping the 3.0.x line of Tapestry alive and healthy is best for the
> community and the fixes you've put in are much needed.
> 
> All tests pass?
> 
> I only vaguely caught the commit messages.... was a method added to
> IEngine?   I saw it added to the MockEngine with a comment about
> IEngine.  That seems fairly dramatic if a method was added to an
> interface - that could certainly break builds for someone upgrading.
> If I'm mistaken, please disregard.
> 
>         Erik
> 
> On Mar 18, 2005, at 8:18 PM, Paul Ferraro wrote:
> 
> > I finished patching/fixing all of the big issues identified with the
> > last release.  With any luck, this will be the last release for the
> > 3.0 branch.
> > This vote will run for one week.  A +1 vote is to release Tapestry
> > 3.0.3.  I will be able to start the release once the votes are
> > tallied.
> >
> > To summarize, the 3.0.3 release will contain the following changes:
> > * Fixes security flaw in asset service.
> > * JanitorThread now terminates explicitly when servlet is destroyed.
> > Interruption properly terminates thread during sweep operation.
> > * Fixed bug preventing DatePicker calendar window from closing
> > automatically if onchange event handler is not specified.
> > * DatePicker onchange event now only fires when date changes.
> > * Patch for bad translation in ValidationStrings_zh_TW.properties
> > * Patch for bad translation in ValidationStrings_zh_CN.properties
> > * Fixed incorrect test for enabling rendering of element in
> > FormConditional component.
> > * Fixes missing type attribute of script tag in Body component.
> > * Fixes improper engine cleanup when client aborts a request.
> > * Build scripts are now Java 1.5 friendly.
> >
> > Paul Ferraro: +1 (binding)
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org 
> > For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org 
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org 
> 
>

---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org