You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Paul Ferraro <pm...@columbia.edu> on 2005/03/26 06:01:03 UTC
[DISCUSS] Release 3.0.3-rc-1
Before I send the official [RESULT] email, I'd like some help clarifying
the results from the vote (see below).
Although most have voted +1, a significant third of the commiters (i.e.
Richard, Erik, Mind Bridge) have expressed a strong interest in a
release candidate prior to a final 3.0.3. To summarize, the concern is
regarding a new method to the IEngine interface and the impacts of the
asset service security fix.
Personally, I doubt that a release candidate is necessary for a few reasons:
1. Although it is technically possible that someone out there uses
their own IEngine implementation that does not extend from
AbstractEngine, it's pretty unlikely.
2. The asset service security fix has already been exposed to the
community in 3.1-alpha-1.
I'm already using a build from cvs in several production systems without
issues as we speak. Has anyone else tried out the latest 3.0-branch yet?
So what's it going to be? Do I tack on "-rc-1" to the result email? or
send it out as is?
Paul
============================================
[RESULT] Release 3.0.3
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.
Binding votes:
Paul Ferraro: +1
Harish Krishnaswamy: +1
Richard Lewis-Shell: +0
Mind Bridge: +1
Howard Lewis Ship: +1
Tsvetelin Saykov: +1
David Solis: +1
Erik Hatcher +0
Geoff Longman: +0
Non-binding votes:
Matthew Mead: +1
Brian Wallace: +1
Enrique Zamudio: +1
Jamie Orchard-Hays: +1
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: [DISCUSS] Release 3.0.3-rc-1
Posted by Geoff Longman <gl...@gmail.com>.
+1 (no rc-1)
Geoff
On Sat, 26 Mar 2005 04:51:15 -0500, Erik Hatcher
<er...@ehatchersolutions.com> wrote:
> I'm +1 for a regular 3.0.3 release. Worst case we follow up with a
> 3.0.4 release if anything is amiss.
>
> Erik
>
> On Mar 26, 2005, at 12:01 AM, Paul Ferraro wrote:
>
> > Before I send the official [RESULT] email, I'd like some help
> > clarifying the results from the vote (see below).
> > Although most have voted +1, a significant third of the commiters
> > (i.e. Richard, Erik, Mind Bridge) have expressed a strong interest in
> > a release candidate prior to a final 3.0.3. To summarize, the concern
> > is regarding a new method to the IEngine interface and the impacts of
> > the asset service security fix.
> >
> > Personally, I doubt that a release candidate is necessary for a few
> > reasons:
> > 1. Although it is technically possible that someone out there uses
> > their own IEngine implementation that does not extend from
> > AbstractEngine, it's pretty unlikely.
> > 2. The asset service security fix has already been exposed to the
> > community in 3.1-alpha-1.
> >
> > I'm already using a build from cvs in several production systems
> > without issues as we speak. Has anyone else tried out the latest
> > 3.0-branch yet?
> >
> > So what's it going to be? Do I tack on "-rc-1" to the result email?
> > or send it out as is?
> >
> > Paul
> >
> > ============================================
> > [RESULT] Release 3.0.3
> >
> > 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.
> >
> > Binding votes:
> > Paul Ferraro: +1
> > Harish Krishnaswamy: +1
> > Richard Lewis-Shell: +0
> > Mind Bridge: +1
> > Howard Lewis Ship: +1
> > Tsvetelin Saykov: +1
> > David Solis: +1
> > Erik Hatcher +0
> > Geoff Longman: +0
> >
> > Non-binding votes:
> > Matthew Mead: +1
> > Brian Wallace: +1
> > Enrique Zamudio: +1
> > Jamie Orchard-Hays: +1
> >
> >
> > ---------------------------------------------------------------------
> > 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
Re: [DISCUSS] Release 3.0.3-rc-1
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
I'm +1 for a regular 3.0.3 release. Worst case we follow up with a
3.0.4 release if anything is amiss.
Erik
On Mar 26, 2005, at 12:01 AM, Paul Ferraro wrote:
> Before I send the official [RESULT] email, I'd like some help
> clarifying the results from the vote (see below).
> Although most have voted +1, a significant third of the commiters
> (i.e. Richard, Erik, Mind Bridge) have expressed a strong interest in
> a release candidate prior to a final 3.0.3. To summarize, the concern
> is regarding a new method to the IEngine interface and the impacts of
> the asset service security fix.
>
> Personally, I doubt that a release candidate is necessary for a few
> reasons:
> 1. Although it is technically possible that someone out there uses
> their own IEngine implementation that does not extend from
> AbstractEngine, it's pretty unlikely.
> 2. The asset service security fix has already been exposed to the
> community in 3.1-alpha-1.
>
> I'm already using a build from cvs in several production systems
> without issues as we speak. Has anyone else tried out the latest
> 3.0-branch yet?
>
> So what's it going to be? Do I tack on "-rc-1" to the result email?
> or send it out as is?
>
> Paul
>
> ============================================
> [RESULT] Release 3.0.3
>
> 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.
>
> Binding votes:
> Paul Ferraro: +1
> Harish Krishnaswamy: +1
> Richard Lewis-Shell: +0
> Mind Bridge: +1
> Howard Lewis Ship: +1
> Tsvetelin Saykov: +1
> David Solis: +1
> Erik Hatcher +0
> Geoff Longman: +0
>
> Non-binding votes:
> Matthew Mead: +1
> Brian Wallace: +1
> Enrique Zamudio: +1
> Jamie Orchard-Hays: +1
>
>
> ---------------------------------------------------------------------
> 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
Re: [DISCUSS] Release 3.0.3-rc-1
Posted by Richard Lewis-Shell <rl...@mac.com>.
I still think an RC is a good idea, but it looks like you've got more
than enough +1's to just release it as 3.0.3.
Richard
Paul Ferraro wrote:
> Before I send the official [RESULT] email, I'd like some help clarifying
> the results from the vote (see below).
> Although most have voted +1, a significant third of the commiters (i.e.
> Richard, Erik, Mind Bridge) have expressed a strong interest in a
> release candidate prior to a final 3.0.3. To summarize, the concern is
> regarding a new method to the IEngine interface and the impacts of the
> asset service security fix.
>
> Personally, I doubt that a release candidate is necessary for a few
> reasons:
> 1. Although it is technically possible that someone out there uses
> their own IEngine implementation that does not extend from
> AbstractEngine, it's pretty unlikely.
> 2. The asset service security fix has already been exposed to the
> community in 3.1-alpha-1.
>
> I'm already using a build from cvs in several production systems without
> issues as we speak. Has anyone else tried out the latest 3.0-branch yet?
>
> So what's it going to be? Do I tack on "-rc-1" to the result email? or
> send it out as is?
>
> Paul
>
> ============================================
> [RESULT] Release 3.0.3
>
> 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.
>
> Binding votes:
> Paul Ferraro: +1
> Harish Krishnaswamy: +1
> Richard Lewis-Shell: +0
> Mind Bridge: +1
> Howard Lewis Ship: +1
> Tsvetelin Saykov: +1
> David Solis: +1
> Erik Hatcher +0
> Geoff Longman: +0
>
> Non-binding votes:
> Matthew Mead: +1
> Brian Wallace: +1
> Enrique Zamudio: +1
> Jamie Orchard-Hays: +1
>
>
> ---------------------------------------------------------------------
> 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