Re: [VOTE] Struts 1.1 Final Release

[Ted Husted]

Arron,

In all likelihood, as soon as you get around to handling this, we may 
have applied some other small patches (like finishing putting the action 
property on the rest of the tags), and we will be ready to pop-out 
another milestone.

Moving forward, I think we should let the state of the CVS decide when 
it's time for another release. If any of us post a patch that needs to 
get out into the hands of production teams, then we should roll a 
release. Those numbers between the dots are integers, and we should 
treat them as such =;0)

It's important to remember that a release is a majority vote. Any one of 
us can tag the CVS and roll a release whenever we like. All it takes to 
get it out the door is three binding +1's and more positive votes than 
negative votes. So, release *.* can be ready whenever you are =:0)

On a related note, the one thing we should be careful about is allowing 
product changes that would foil a release. The Commons Resource 
initiative (which I support, use, and will continue to help with) is a 
good example. I would be leery of moving the main trunk over to Commons 
Resources until C/R is out of the sandbox and ready for beta. I would 
especially insist that any other product changes be released before 
making a dependency change, lest innocent bystanders get stuck behind 
unexpected issues. (Been there, did that, won't let it happen again.)

But, as far something like this goes, make the fix, and I'll help roll 
the release =:0)

-Ted.

Arron Bates wrote:
-0

Only because there is a bug raised against the nested tags where it's dropping
a reference for included/tiles files in some strange instance.
I would have liked to have confirmed, patched and squished/handled it, but my
last few weeks have been crazy with moving to the US. I wont be able to get
onto it until thurday next week until after the move. Would be sweet if 1.1
could wait until then, but anyways.
Just need to say that a version cut now is done with possible issue.

Anyone's welcome to dive in there and have a play to see if it is an issue...

With obvious other priorities, I'll probably just gruble a little and wait to
have it handled for 1.2 or 1.1.1  :P
Arron.




Ted Husted wrote:


Since no significant issues have arisen in response to Struts 1.1 RC2, 
I propose that we release the tip of the main trunk in CVS as the 
Struts 1.1 Final release. I have checked in a proposed release plan, 
which is available for review on the Struts web site:

http://jakarta.apache.org/struts/proposals/release-plan-1.1.html

Release plans must pass by a majority vote of committers on the project,
but all other interested parties are welcome to cast their votes (and/or
make comments or suggestions on the plan) as well.
--
Vote:  Struts 1.1 Final Release Plan
[ ] +1 I am in favor of the release, and will help support it
[ ] +0 I am in favor of the release, but am unable to help support it
[ ] -0 I am not in favor of the release
[ ] -1 I am against this proposal (must include a reason).
-
I am +1 on the Struts 1.1 Final release plan.

-Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



--
Ted Husted,
Struts in Action 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[Arron Bates]

-0

Only because there is a bug raised against the nested tags where it's dropping
a reference for included/tiles files in some strange instance.

I would have liked to have confirmed, patched and squished/handled it, but my
last few weeks have been crazy with moving to the US. I wont be able to get
onto it until thurday next week until after the move. Would be sweet if 1.1
could wait until then, but anyways.

Just need to say that a version cut now is done with possible issue.

Anyone's welcome to dive in there and have a play to see if it is an issue...


With obvious other priorities, I'll probably just gruble a little and wait to
have it handled for 1.2 or 1.1.1  :P


Arron.



> Ted Husted wrote:
> 
> > Since no significant issues have arisen in response to Struts 1.1 RC2, 
> > I propose that we release the tip of the main trunk in CVS as the 
> > Struts 1.1 Final release. I have checked in a proposed release plan, 
> > which is available for review on the Struts web site:
> >
> >  http://jakarta.apache.org/struts/proposals/release-plan-1.1.html
> >
> > Release plans must pass by a majority vote of committers on the project,
> > but all other interested parties are welcome to cast their votes (and/or
> > make comments or suggestions on the plan) as well.
> >
> > --
> >  Vote:  Struts 1.1 Final Release Plan
> >  [ ] +1 I am in favor of the release, and will help support it
> >  [ ] +0 I am in favor of the release, but am unable to help support it
> >  [ ] -0 I am not in favor of the release
> >  [ ] -1 I am against this proposal (must include a reason).
> >  -
> >
> > I am +1 on the Struts 1.1 Final release plan.
> >
> >
> > -Ted.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Struts 1.1 Final Release

[David Graham]

--- Etienne_Labonté <[EMAIL PROTECTED]> wrote:
> I think I remember you saying you would release 1.2 ASAP after removing
> all
> the deprecated stuff. I would like that very much since I have to
> comment
> out a few deprecated things in 1.1 and build my own Struts.jar

No, 1.2 will include a move to commons-resources and other minor
enhancements as well as removing the deprecated stuff.

David

> 
> Etienne
> 
> -Original Message-
> From: David Graham [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, June 26, 2003 11:13 AM
> To: Struts Developers List
> Subject: Re: [VOTE] Struts 1.1 Final Release
> 
> > Moving forward, if someone were to start to add another enhancement
> (or
> > "product change") while another was already unreleased in the nightly 
> > build, I would veto the change and force a point release. (And if I 
> > didn't I'm sure someone else around here now would.) The justification
> 
> > being that we simply don't have the resources to support releasing so 
> > many changes at once.
> 
> Just for clarification, each enhancement doesn't need it's own release,
> just major changes like moving to commons-resources.  I see each point
> release as having at most one major change and I will join Ted in
> vetoing
> any major changes occuring while another is in progress.
> 
> I've personally signed up for about 10 minor enhancements to 1.2 and
> will
> help with the commons-resources move.  When that move is done we should
> cut 1.2.
> 
> David
> 
> > 
> > The other issue was moving dependencies to other products. We should
> now
> > 
> > make a point release before (or after) moving or adding any 
> > dependencies, even if it is to a Commons product. The next thing on my
> 
> > radar is moving some dependencies to Commons Resources. So as soon as
> we
> > 
> > do that and the code seems stable, it should trigger a point-release.
> > 
> > Since we are all volunteers here, what gets done depends on who is
> > willing to actually do something. There is no hierarchy; individual
> > committers decide what they want to work on, and then other developers
> > chip in as they wish. But, we can each veto any product change we
> > believe is technically unsound, which provides a check and balance.
> > 
> > Most of us are working stiffs, so we tend to do things that we need
> for 
> > our own applications. The vast majority of changes to Struts come
> about 
> > from developers submitting patches they made so that their own 
> > applications became easier to write.
> > 
> > -Ted.
> > 
> > 
> > -- 
> > Ted Husted,
> > Struts in Action <http://husted.com/struts/book.html>
> > 
> > 
> > 
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> 
> 
> __
> Do you Yahoo!?
> SBC Yahoo! DSL - Now only $29.95 per month!
> http://sbc.yahoo.com
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Struts 1.1 Final Release

[Etienne Labonté]

I think I remember you saying you would release 1.2 ASAP after removing all
the deprecated stuff. I would like that very much since I have to comment
out a few deprecated things in 1.1 and build my own Struts.jar


Etienne

-Original Message-
From: David Graham [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 26, 2003 11:13 AM
To: Struts Developers List
Subject: Re: [VOTE] Struts 1.1 Final Release

> Moving forward, if someone were to start to add another enhancement (or
> "product change") while another was already unreleased in the nightly 
> build, I would veto the change and force a point release. (And if I 
> didn't I'm sure someone else around here now would.) The justification 
> being that we simply don't have the resources to support releasing so 
> many changes at once.

Just for clarification, each enhancement doesn't need it's own release,
just major changes like moving to commons-resources.  I see each point
release as having at most one major change and I will join Ted in vetoing
any major changes occuring while another is in progress.

I've personally signed up for about 10 minor enhancements to 1.2 and will
help with the commons-resources move.  When that move is done we should
cut 1.2.

David

> 
> The other issue was moving dependencies to other products. We should now
> 
> make a point release before (or after) moving or adding any 
> dependencies, even if it is to a Commons product. The next thing on my 
> radar is moving some dependencies to Commons Resources. So as soon as we
> 
> do that and the code seems stable, it should trigger a point-release.
> 
> Since we are all volunteers here, what gets done depends on who is
> willing to actually do something. There is no hierarchy; individual
> committers decide what they want to work on, and then other developers
> chip in as they wish. But, we can each veto any product change we
> believe is technically unsound, which provides a check and balance.
> 
> Most of us are working stiffs, so we tend to do things that we need for 
> our own applications. The vast majority of changes to Struts come about 
> from developers submitting patches they made so that their own 
> applications became easier to write.
> 
> -Ted.
> 
> 
> -- 
> Ted Husted,
> Struts in Action <http://husted.com/struts/book.html>
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[Cedric Dumoulin]

 +1

 Cedric

Ted Husted wrote:

Since no significant issues have arisen in response to Struts 1.1 RC2, 
I propose that we release the tip of the main trunk in CVS as the 
Struts 1.1 Final release. I have checked in a proposed release plan, 
which is available for review on the Struts web site:

 http://jakarta.apache.org/struts/proposals/release-plan-1.1.html

Release plans must pass by a majority vote of committers on the project,
but all other interested parties are welcome to cast their votes (and/or
make comments or suggestions on the plan) as well.
--
 Vote:  Struts 1.1 Final Release Plan
 [ ] +1 I am in favor of the release, and will help support it
 [ ] +0 I am in favor of the release, but am unable to help support it
 [ ] -0 I am not in favor of the release
 [ ] -1 I am against this proposal (must include a reason).
 -
I am +1 on the Struts 1.1 Final release plan.

-Ted.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[Martin Cooper]

On Thu, 26 Jun 2003, Ted Husted wrote:

> --
>   Vote:  Struts 1.1 Final Release Plan
>   [X] +1 I am in favor of the release, and will help support it
>   [ ] +0 I am in favor of the release, but am unable to help support it
>   [ ] -0 I am not in favor of the release
>   [ ] -1 I am against this proposal (must include a reason).
>   -

Yippee!

--
Martin Cooper


>
> I am +1 on the Struts 1.1 Final release plan.
>
>
> -Ted.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[Craig R. McClanahan]

+1!!!

Hurray!!!

Craig

On Thu, 26 Jun 2003, Ted Husted wrote:

> Date: Thu, 26 Jun 2003 07:42:37 -0400
> From: Ted Husted <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [VOTE] Struts 1.1 Final Release
>
> Since no significant issues have arisen in response to Struts 1.1 RC2, I
> propose that we release the tip of the main trunk in CVS as the Struts
> 1.1 Final release. I have checked in a proposed release plan, which is
> available for review on the Struts web site:
>
>   http://jakarta.apache.org/struts/proposals/release-plan-1.1.html
>
> Release plans must pass by a majority vote of committers on the project,
> but all other interested parties are welcome to cast their votes (and/or
> make comments or suggestions on the plan) as well.
>
> --
>   Vote:  Struts 1.1 Final Release Plan
>   [ ] +1 I am in favor of the release, and will help support it
>   [ ] +0 I am in favor of the release, but am unable to help support it
>   [ ] -0 I am not in favor of the release
>   [ ] -1 I am against this proposal (must include a reason).
>   -
>
> I am +1 on the Struts 1.1 Final release plan.
>
>
> -Ted.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[Rob Leland]

-- 

 Vote:  Struts 1.1 Final Release Plan
 [X] +1 I am in favor of the release, and will help support it
 [ ] +0 I am in favor of the release, but am unable to help support it
 [ ] -0 I am not in favor of the release
 [ ] -1 I am against this proposal (must include a reason).
 - 





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[David Graham]

> Moving forward, if someone were to start to add another enhancement (or
> "product change") while another was already unreleased in the nightly 
> build, I would veto the change and force a point release. (And if I 
> didn't I'm sure someone else around here now would.) The justification 
> being that we simply don't have the resources to support releasing so 
> many changes at once.

Just for clarification, each enhancement doesn't need it's own release,
just major changes like moving to commons-resources.  I see each point
release as having at most one major change and I will join Ted in vetoing
any major changes occuring while another is in progress.

I've personally signed up for about 10 minor enhancements to 1.2 and will
help with the commons-resources move.  When that move is done we should
cut 1.2.

David

> 
> The other issue was moving dependencies to other products. We should now
> 
> make a point release before (or after) moving or adding any 
> dependencies, even if it is to a Commons product. The next thing on my 
> radar is moving some dependencies to Commons Resources. So as soon as we
> 
> do that and the code seems stable, it should trigger a point-release.
> 
> Since we are all volunteers here, what gets done depends on who is
> willing to actually do something. There is no hierarchy; individual
> committers decide what they want to work on, and then other developers
> chip in as they wish. But, we can each veto any product change we
> believe is technically unsound, which provides a check and balance.
> 
> Most of us are working stiffs, so we tend to do things that we need for 
> our own applications. The vast majority of changes to Struts come about 
> from developers submitting patches they made so that their own 
> applications became easier to write.
> 
> -Ted.
> 
> 
> -- 
> Ted Husted,
> Struts in Action 
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[James Mitchell]

On Thursday 26 June 2003 07:42, Ted Husted wrote:
> --
>   Vote:  Struts 1.1 Final Release Plan
>   [X] +1 I am in favor of the release, and will help support it
>   [ ] +0 I am in favor of the release, but am unable to help support it
>   [ ] -0 I am not in favor of the release
>   [ ] -1 I am against this proposal (must include a reason).
>   -
>
> I am +1 on the Struts 1.1 Final release plan.
>
>
> -Ted.
>

Now THIS is a nice way to start my vacation!

BTW, if anyone just happens to be near the Chesapeake Bay and wants to enjoy a 
cold beer and some great fishing, let me know by Saturday morning and I'll 
put a few extra on ice for ya.

I'll be back after the 4th of July weekend.  


W Ho!!!



-- 
James Mitchell
Software Developer/Struts Evangelist
http://www.struts-atlanta.org
770-822-3359
AIM:jmitchtx



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Struts 1.1 Final Release

[James Holmes]

+1

-James

-Original Message-
From: Ted Husted [mailto:[EMAIL PROTECTED] 
Sent: Thursday, June 26, 2003 6:43 AM
To: [EMAIL PROTECTED]
Subject: [VOTE] Struts 1.1 Final Release

Since no significant issues have arisen in response to Struts 1.1 RC2, I

propose that we release the tip of the main trunk in CVS as the Struts 
1.1 Final release. I have checked in a proposed release plan, which is 
available for review on the Struts web site:

  http://jakarta.apache.org/struts/proposals/release-plan-1.1.html

Release plans must pass by a majority vote of committers on the project,
but all other interested parties are welcome to cast their votes (and/or
make comments or suggestions on the plan) as well.


--
  Vote:  Struts 1.1 Final Release Plan
  [ ] +1 I am in favor of the release, and will help support it
  [ ] +0 I am in favor of the release, but am unable to help support it
  [ ] -0 I am not in favor of the release
  [ ] -1 I am against this proposal (must include a reason).
 

-

I am +1 on the Struts 1.1 Final release plan.


-Ted.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Struts 1.1 Final Release

[James Turner]

  Vote:  Struts 1.1 Final Release Plan
  [X] +1 I am in favor of the release, and will help support it
  [ ] +0 I am in favor of the release, but am unable to help support it
  [ ] -0 I am not in favor of the release
  [ ] -1 I am against this proposal (must include a reason).
 

-

BTW, Lucifer just called and he needs a pair of ice skates :-)

James



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Struts 1.1 Final Release

[Karr, David]

> -Original Message-
> From: Ted Husted [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 26, 2003 4:43 AM
> To: [EMAIL PROTECTED]
> Subject: [VOTE] Struts 1.1 Final Release
> 
> Since no significant issues have arisen in response to Struts 1.1 RC2,
I
> propose that we release the tip of the main trunk in CVS as the Struts
> 1.1 Final release. I have checked in a proposed release plan, which is
> available for review on the Struts web site:
> 
>   http://jakarta.apache.org/struts/proposals/release-plan-1.1.html
> 
> Release plans must pass by a majority vote of committers on the
project,
> but all other interested parties are welcome to cast their votes
(and/or
> make comments or suggestions on the plan) as well.
> 
>

--
>   Vote:  Struts 1.1 Final Release Plan
>   [X] +1 I am in favor of the release, and will help support it
>   [ ] +0 I am in favor of the release, but am unable to help support
it
>   [ ] -0 I am not in favor of the release
>   [ ] -1 I am against this proposal (must include a reason).
>


Hallelujah.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[Ted Husted]

Nicolas De Loof wrote:
> Just a question about releasse process : it seems 1.1 has too much
> fonctional enhancements to "quickly" get a release,
> and I've read here that future versions will get less improvement, so
> that it can be release a simplier way. How will
> commiters decide future enhancements ?
The issue wasn't so much that there were so many enhancements, but that
we neglected to make point releases along the way. So, by rights, this 
is really like Struts 1.8. With 20:20 hindsight, there should have been 
point releases after adding the nested-taglib, after adding module 
support, after adding the validator, after adding tiles, after adding 
the JSTL lib, and so forth.

Moving forward, if someone were to start to add another enhancement (or
"product change") while another was already unreleased in the nightly 
build, I would veto the change and force a point release. (And if I 
didn't I'm sure someone else around here now would.) The justification 
being that we simply don't have the resources to support releasing so 
many changes at once.

The other issue was moving dependencies to other products. We should now 
make a point release before (or after) moving or adding any 
dependencies, even if it is to a Commons product. The next thing on my 
radar is moving some dependencies to Commons Resources. So as soon as we 
do that and the code seems stable, it should trigger a point-release.

Since we are all volunteers here, what gets done depends on who is
willing to actually do something. There is no hierarchy; individual
committers decide what they want to work on, and then other developers
chip in as they wish. But, we can each veto any product change we
believe is technically unsound, which provides a check and balance.
Most of us are working stiffs, so we tend to do things that we need for 
our own applications. The vast majority of changes to Struts come about 
from developers submitting patches they made so that their own 
applications became easier to write.

-Ted.

--
Ted Husted,
Struts in Action 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[David Graham]

--- Ted Husted <[EMAIL PROTECTED]> wrote:
> Since no significant issues have arisen in response to Struts 1.1 RC2, I
> 
> propose that we release the tip of the main trunk in CVS as the Struts 
> 1.1 Final release. I have checked in a proposed release plan, which is 
> available for review on the Struts web site:
> 
>   http://jakarta.apache.org/struts/proposals/release-plan-1.1.html
> 
> Release plans must pass by a majority vote of committers on the project,
> but all other interested parties are welcome to cast their votes (and/or
> make comments or suggestions on the plan) as well.
> 
>
--
>   Vote:  Struts 1.1 Final Release Plan
>   [X] +1 I am in favor of the release, and will help support it
>   [ ] +0 I am in favor of the release, but am unable to help support it
>   [ ] -0 I am not in favor of the release
>   [ ] -1 I am against this proposal (must include a reason).
>  
>
-


Anyone want to help me figure out these 2 ConcurrentModificationExceptions
before Saturday :-) ?

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21091
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21108

David


> I am +1 on the Struts 1.1 Final release plan.
> 
> 
> -Ted.
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [VOTE] Struts 1.1 Final Release

[Arnaud HERITIER]

Why it is wrote that struts examples shall operate successfully in tomcat
4.1.18 whereas it is the 4.1.24 which is the current production release for
servlet 2.3 / JSP 1.2 ???

I'm not commiter but you have my +0 !!

Arnaud.

> -Message d'origine-
> De : Ted Husted [mailto:[EMAIL PROTECTED]
> Envoye : jeudi 26 juin 2003 13:43
> A : [EMAIL PROTECTED]
> Objet : [VOTE] Struts 1.1 Final Release
>
>
> Since no significant issues have arisen in response to Struts
> 1.1 RC2, I
> propose that we release the tip of the main trunk in CVS as
> the Struts
> 1.1 Final release. I have checked in a proposed release plan,
> which is
> available for review on the Struts web site:
>
>   http://jakarta.apache.org/struts/proposals/release-plan-1.1.html
>
> Release plans must pass by a majority vote of committers on
> the project,
> but all other interested parties are welcome to cast their
> votes (and/or
> make comments or suggestions on the plan) as well.
>
> --
> 
>   Vote:  Struts 1.1 Final Release Plan
>   [ ] +1 I am in favor of the release, and will help support it
>   [ ] +0 I am in favor of the release, but am unable to help
> support it
>   [ ] -0 I am not in favor of the release
>   [ ] -1 I am against this proposal (must include a reason).
>
> --
> ---
>
> I am +1 on the Struts 1.1 Final release plan.
>
>
> -Ted.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [VOTE] Struts 1.1 Final Release

[Nicolas De Loof]

>
> Release plans must pass by a majority vote of committers on the project,
> but all other interested parties are welcome to cast their votes (and/or
> make comments or suggestions on the plan) as well.
>
> --
>   Vote:  Struts 1.1 Final Release Plan
>   [ ] +1 I am in favor of the release, and will help support it
>   [ ] +0 I am in favor of the release, but am unable to help support it
>   [ ] -0 I am not in favor of the release
>   [ ] -1 I am against this proposal (must include a reason).
>   -
>

As a non-commiter but enthusiast Struts user you get my +1


Just a question about releasse process : it seems 1.1 has too much fonctional 
enhancements to "quickly" get a release,
and I've read here that future versions will get less improvement, so that it can be 
release a simplier way. How will
commiters decide future enhancements ?

Nico.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]