The missing release plan

[Martin Cooper <ma...@tumbleweed.com>]

Through informal discussion, we decided to go to Struts 1.1 Beta 1 on March
4th, which is today. However, I've realised that I dropped the ball, and did
not produce a release plan, to be voted on by the committers. So the
question is, how should I best recover?

Here are a couple of options:

1) Continue with a Beta 1 release in the next day or so, regardless of a
vote on the release plan, but depending on when the crucial fixes are
checked in.

2) Post a release plan ASAP, and await a "go" vote before proceeding with
the Beta 1 release.

Other suggestions are welcome.

Committers, please let me know what you would like me to do in this respect.

--
Martin Cooper



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: The missing release plan

["Craig R. McClanahan" <cr...@apache.org>]

Let's propose a (revised) plan and go forth from there.  Martin, I didn't
get my deliverables done on time either, so don't feel *too* bad.

Craig


On Tue, 5 Mar 2002, Arron Bates wrote:

> Date: Tue, 05 Mar 2002 17:35:52 +1100
> From: Arron Bates <ar...@keyboardmonkey.com>
> Reply-To: Struts Developers List <st...@jakarta.apache.org>
> To: Struts Developers List <st...@jakarta.apache.org>
> Subject: Re: The missing release plan
>
> 2
>
> That way there's less room for people feeling their intended effort
> missed the boat.
>
> Arron.
>
> Martin Cooper wrote:
>
> >Through informal discussion, we decided to go to Struts 1.1 Beta 1 on March
> >4th, which is today. However, I've realised that I dropped the ball, and did
> >not produce a release plan, to be voted on by the committers. So the
> >question is, how should I best recover?
> >
> >Here are a couple of options:
> >
> >1) Continue with a Beta 1 release in the next day or so, regardless of a
> >vote on the release plan, but depending on when the crucial fixes are
> >checked in.
> >
> >2) Post a release plan ASAP, and await a "go" vote before proceeding with
> >the Beta 1 release.
> >
> >Other suggestions are welcome.
> >
> >Committers, please let me know what you would like me to do in this respect.
> >
> >--
> >Martin Cooper
> >
> >
> >
> >--
> >To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> >For additional commands, e-mail: <ma...@jakarta.apache.org>
> >
>
>
>
> --
> To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: The missing release plan

[Arron Bates <ar...@keyboardmonkey.com>]

2

That way there's less room for people feeling their intended effort 
missed the boat.

Arron.

Martin Cooper wrote:

>Through informal discussion, we decided to go to Struts 1.1 Beta 1 on March
>4th, which is today. However, I've realised that I dropped the ball, and did
>not produce a release plan, to be voted on by the committers. So the
>question is, how should I best recover?
>
>Here are a couple of options:
>
>1) Continue with a Beta 1 release in the next day or so, regardless of a
>vote on the release plan, but depending on when the crucial fixes are
>checked in.
>
>2) Post a release plan ASAP, and await a "go" vote before proceeding with
>the Beta 1 release.
>
>Other suggestions are welcome.
>
>Committers, please let me know what you would like me to do in this respect.
>
>--
>Martin Cooper
>
>
>
>--
>To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
>For additional commands, e-mail: <ma...@jakarta.apache.org>
>



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>