You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by David Blevins <da...@visi.com> on 2005/07/25 23:59:47 UTC
Attacking M4
Alright, here is the deal on M4. We have OSCON coming up and from my
experience, if we don't get M4 out the door this week, then we won't
see it till the week after OSCON. I actually tried to cut M3 at
OSCON last year and we all know how that went.
If we don't get M4 out the door this week, our hopes of having M5 by
the 15th are lost. Assuming we don't want this to happen, here is my
attack plan:
=ATTACK PLAN==========
LAST ISSUES
- Undeployment issue (GERONIMO-812, David Jencks)
- Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
ServiceMix=>Hiram, tmpOrb=>Dain)
- Web Services startup issue (GERONIMO-785, David Blevins)
- Corba interop problem (GERONIMO-813, Dain Sundstrom)
- Izpack/Tomcat issue (GERONIMO-811, Unassigned)
- Unknown CTS issues (need to clear up GERONIMO-812 to run it
completely)
No sitting on tasks, if you are not going to do it, mark it unassigned.
Issue GERONIMO-811 is unassigned. Can someone either remove the
Tomcat option from the IzPack installer or add a the link to the wiki?
It seems GERONIMO-809 is actually completed, is that right?
THE FINAL STUFF
We have to run the TCK on the final binary, which means we need to
allow for a couple days of just testing the actual geronimo-1.0-
M4.zip that people will download. To even get that far, we need to:
1. [notes] Create release notes for M4 and check them into the QA
branch
2. [svn] Close the QA branch and copy it to tags/v1_0_M4
3. [dist] Cut and sign the binary and source distributions
We are going to need to be done with the remaining JIRA items above
by like Wednesday (best) or Thursday morning in order to do the above
tasks.
I am willing to take care of the svn and dist work. Side-note: I have
to go to a wedding on Friday, so I personally would like to shoot for
Wednesday as Thursday night is too late for me.
Aaron, you willing to do the nice release notes like you did for M3?
====================
Sound good to everyone? Going to assume a lazy consensus otherwise.
-David
RE: Attacking M4
Posted by si...@insession.com.
"Jeff Genender" <jg...@savoirtech.com> wrote on 26/07/2005 10:42:06
AM:
> > -----Original Message-----
> > From: Aaron Mulder [mailto:ammulder@alumni.princeton.edu]
> > Sent: Monday, July 25, 2005 5:59 PM
> > To: dev@geronimo.apache.org
> > Subject: Re: Attacking M4
> >
> > WRT Tomcat, I think we should just comment out that
> > block from the installer config files in M4. The procedure
> > for getting it running is way too arcane, and we have
> > something much better in place in HEAD already.
> > Also, I'd like to see Tomcat get a bit more testing before
> > making noise about it in a release.
> >
>
> +1 for both testing and waiting for M5 for the "good stuff". Perhaps
this
> is a great time for me to bug the community to say..."Please test your
> applications on Tomcat" ;-)
I'll remove the Tomcat stuff from the M4 installer tonight (Sydney time).
John
>
> > I can certainly take the todo for the release notes.
> >
> > Thanks,
> > Aaron
> >
> > On Mon, 25 Jul 2005, David Blevins wrote:
> > > Alright, here is the deal on M4. We have OSCON coming up
> > and from my
> > > experience, if we don't get M4 out the door this week, then
> > we won't
> > > see it till the week after OSCON. I actually tried to cut
> > M3 at OSCON
> > > last year and we all know how that went.
> > >
> > > If we don't get M4 out the door this week, our hopes of
> > having M5 by
> > > the 15th are lost. Assuming we don't want this to happen,
> > here is my
> > > attack plan:
> > >
> > > =ATTACK PLAN==========
> > >
> > > LAST ISSUES
> > >
> > > - Undeployment issue (GERONIMO-812, David Jencks)
> > > - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> > > ServiceMix=>Hiram, tmpOrb=>Dain)
> > > - Web Services startup issue (GERONIMO-785, David Blevins)
> > > - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> > > - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> > > - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> > > completely)
> > >
> > > No sitting on tasks, if you are not going to do it, mark it
> > unassigned.
> > >
> > > Issue GERONIMO-811 is unassigned. Can someone either remove the
> > > Tomcat option from the IzPack installer or add a the link
> > to the wiki?
> > >
> > > It seems GERONIMO-809 is actually completed, is that right?
> > >
> > > THE FINAL STUFF
> > >
> > > We have to run the TCK on the final binary, which means we need to
> > > allow for a couple days of just testing the actual geronimo-1.0-
> > > M4.zip that people will download. To even get that far, we need to:
> > >
> > > 1. [notes] Create release notes for M4 and check them
> > into the QA
> > > branch
> > > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > > 3. [dist] Cut and sign the binary and source distributions
> > >
> > > We are going to need to be done with the remaining JIRA
> > items above by
> > > like Wednesday (best) or Thursday morning in order to do the above
> > > tasks.
> > >
> > > I am willing to take care of the svn and dist work.
> > Side-note: I have
> > > to go to a wedding on Friday, so I personally would like to
> > shoot for
> > > Wednesday as Thursday night is too late for me.
> > >
> > > Aaron, you willing to do the nice release notes like you did for M3?
> > >
> > > ====================
> > >
> > > Sound good to everyone? Going to assume a lazy consensus otherwise.
> > >
> > > -David
> > >
> > >
> >
>
>
RE: Attacking M4
Posted by Jeff Genender <jg...@savoirtech.com>.
> -----Original Message-----
> From: Aaron Mulder [mailto:ammulder@alumni.princeton.edu]
> Sent: Monday, July 25, 2005 5:59 PM
> To: dev@geronimo.apache.org
> Subject: Re: Attacking M4
>
> WRT Tomcat, I think we should just comment out that
> block from the installer config files in M4. The procedure
> for getting it running is way too arcane, and we have
> something much better in place in HEAD already.
> Also, I'd like to see Tomcat get a bit more testing before
> making noise about it in a release.
>
+1 for both testing and waiting for M5 for the "good stuff". Perhaps this
is a great time for me to bug the community to say..."Please test your
applications on Tomcat" ;-)
> I can certainly take the todo for the release notes.
>
> Thanks,
> Aaron
>
> On Mon, 25 Jul 2005, David Blevins wrote:
> > Alright, here is the deal on M4. We have OSCON coming up
> and from my
> > experience, if we don't get M4 out the door this week, then
> we won't
> > see it till the week after OSCON. I actually tried to cut
> M3 at OSCON
> > last year and we all know how that went.
> >
> > If we don't get M4 out the door this week, our hopes of
> having M5 by
> > the 15th are lost. Assuming we don't want this to happen,
> here is my
> > attack plan:
> >
> > =ATTACK PLAN==========
> >
> > LAST ISSUES
> >
> > - Undeployment issue (GERONIMO-812, David Jencks)
> > - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> > ServiceMix=>Hiram, tmpOrb=>Dain)
> > - Web Services startup issue (GERONIMO-785, David Blevins)
> > - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> > - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> > - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> > completely)
> >
> > No sitting on tasks, if you are not going to do it, mark it
> unassigned.
> >
> > Issue GERONIMO-811 is unassigned. Can someone either remove the
> > Tomcat option from the IzPack installer or add a the link
> to the wiki?
> >
> > It seems GERONIMO-809 is actually completed, is that right?
> >
> > THE FINAL STUFF
> >
> > We have to run the TCK on the final binary, which means we need to
> > allow for a couple days of just testing the actual geronimo-1.0-
> > M4.zip that people will download. To even get that far, we need to:
> >
> > 1. [notes] Create release notes for M4 and check them
> into the QA
> > branch
> > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > 3. [dist] Cut and sign the binary and source distributions
> >
> > We are going to need to be done with the remaining JIRA
> items above by
> > like Wednesday (best) or Thursday morning in order to do the above
> > tasks.
> >
> > I am willing to take care of the svn and dist work.
> Side-note: I have
> > to go to a wedding on Friday, so I personally would like to
> shoot for
> > Wednesday as Thursday night is too late for me.
> >
> > Aaron, you willing to do the nice release notes like you did for M3?
> >
> > ====================
> >
> > Sound good to everyone? Going to assume a lazy consensus otherwise.
> >
> > -David
> >
> >
>
Re: Attacking M4
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
WRT Tomcat, I think we should just comment out that block from the
installer config files in M4. The procedure for getting it running is way
too arcane, and we have something much better in place in HEAD already.
Also, I'd like to see Tomcat get a bit more testing before making noise
about it in a release.
I can certainly take the todo for the release notes.
Thanks,
Aaron
On Mon, 25 Jul 2005, David Blevins wrote:
> Alright, here is the deal on M4. We have OSCON coming up and from my
> experience, if we don't get M4 out the door this week, then we won't
> see it till the week after OSCON. I actually tried to cut M3 at
> OSCON last year and we all know how that went.
>
> If we don't get M4 out the door this week, our hopes of having M5 by
> the 15th are lost. Assuming we don't want this to happen, here is my
> attack plan:
>
> =ATTACK PLAN==========
>
> LAST ISSUES
>
> - Undeployment issue (GERONIMO-812, David Jencks)
> - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> ServiceMix=>Hiram, tmpOrb=>Dain)
> - Web Services startup issue (GERONIMO-785, David Blevins)
> - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> completely)
>
> No sitting on tasks, if you are not going to do it, mark it unassigned.
>
> Issue GERONIMO-811 is unassigned. Can someone either remove the
> Tomcat option from the IzPack installer or add a the link to the wiki?
>
> It seems GERONIMO-809 is actually completed, is that right?
>
> THE FINAL STUFF
>
> We have to run the TCK on the final binary, which means we need to
> allow for a couple days of just testing the actual geronimo-1.0-
> M4.zip that people will download. To even get that far, we need to:
>
> 1. [notes] Create release notes for M4 and check them into the QA
> branch
> 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> 3. [dist] Cut and sign the binary and source distributions
>
> We are going to need to be done with the remaining JIRA items above
> by like Wednesday (best) or Thursday morning in order to do the above
> tasks.
>
> I am willing to take care of the svn and dist work. Side-note: I have
> to go to a wedding on Friday, so I personally would like to shoot for
> Wednesday as Thursday night is too late for me.
>
> Aaron, you willing to do the nice release notes like you did for M3?
>
> ====================
>
> Sound good to everyone? Going to assume a lazy consensus otherwise.
>
> -David
>
>
Re: Attacking M4
Posted by Davanum Srinivas <da...@gmail.com>.
Thanks a ton.
-- dims
On 7/25/05, sissonj@insession.com <si...@insession.com> wrote:
> Davanum Srinivas <da...@gmail.com> wrote on 26/07/2005 11:47:05 AM:
>
> > sisson,
> >
> > On 7/25/05, sissonj@insession.com <si...@insession.com> wrote:
> > > Davanum Srinivas <da...@gmail.com> wrote on 26/07/2005 09:22:34 AM:
> > >
> > > > Javamail & Axis...
> > > >
> > > > - Am done with changes to JavaMail. tests are working as well.
> > >
> > > Dims, are you going to build a new release candidate of the javamail
> spec
> > > jar - GERONIMO-802 and update the M4 branch to point to it?
> >
> > Could someone who has done it before do it please? I have no clue
> > about the steps involved.
>
> Ok, I'll do it tonight (Sydney time).
>
> >
> > > Currently both M4 and HEAD are using
> > > geronimo_spec_javamail_version=1.3.1-rc4 which was built before some
> of
> > > you JavaMail spec changes.
> > >
> > > > - We most probably can't squeeze in a new release of Axis this week.
> > > > What do we do? (dated snapshot?)
> > >
> > > Dated build sounds good to me. I don't think it should have SNAPSHOT
> as
> > > part of its version or name, as that would cause maven unnecessarily
> check
> > > for updates for it.
> >
> > Sounds good. Let me review the Axis bugs list and come up a dated
> > build in the next few days.
> >
> > > Thanks,
> > >
> > > John
> > > >
> > > > thanks,
> > > > -- dims
> > > >
> > > > On 7/25/05, David Blevins <da...@visi.com> wrote:
> > > > > Alright, here is the deal on M4. We have OSCON coming up and from
> my
> > > > > experience, if we don't get M4 out the door this week, then we
> won't
> > > > > see it till the week after OSCON. I actually tried to cut M3 at
> > > > > OSCON last year and we all know how that went.
> > > > >
> > > > > If we don't get M4 out the door this week, our hopes of having M5
> by
> > > > > the 15th are lost. Assuming we don't want this to happen, here is
> my
> > > > > attack plan:
> > > > >
> > > > > =ATTACK PLAN==========
> > > > >
> > > > > LAST ISSUES
> > > > >
> > > > > - Undeployment issue (GERONIMO-812, David Jencks)
> > > > > - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> > > > > ServiceMix=>Hiram, tmpOrb=>Dain)
> > > > > - Web Services startup issue (GERONIMO-785, David Blevins)
> > > > > - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> > > > > - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> > > > > - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> > > > > completely)
> > > > >
> > > > > No sitting on tasks, if you are not going to do it, mark it
> > > unassigned.
> > > > >
> > > > > Issue GERONIMO-811 is unassigned. Can someone either remove the
> > > > > Tomcat option from the IzPack installer or add a the link to the
> wiki?
> > > > >
> > > > > It seems GERONIMO-809 is actually completed, is that right?
> > > > >
> > > > > THE FINAL STUFF
> > > > >
> > > > > We have to run the TCK on the final binary, which means we need to
> > > > > allow for a couple days of just testing the actual geronimo-1.0-
> > > > > M4.zip that people will download. To even get that far, we need
> to:
> > > > >
> > > > > 1. [notes] Create release notes for M4 and check them into the
> QA
> > > > > branch
> > > > > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > > > > 3. [dist] Cut and sign the binary and source distributions
> > > > >
> > > > > We are going to need to be done with the remaining JIRA items
> above
> > > > > by like Wednesday (best) or Thursday morning in order to do the
> above
> > > > > tasks.
> > > > >
> > > > > I am willing to take care of the svn and dist work. Side-note: I
> have
> > > > > to go to a wedding on Friday, so I personally would like to shoot
> for
> > > > > Wednesday as Thursday night is too late for me.
> > > > >
> > > > > Aaron, you willing to do the nice release notes like you did for
> M3?
> > > > >
> > > > > ====================
> > > > >
> > > > > Sound good to everyone? Going to assume a lazy consensus
> otherwise.
> > > > >
> > > > > -David
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Davanum Srinivas -http://blogs.cocoondev.org/dims/
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas -http://blogs.cocoondev.org/dims/
>
>
--
Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Attacking M4
Posted by si...@insession.com.
Davanum Srinivas <da...@gmail.com> wrote on 26/07/2005 11:47:05 AM:
> sisson,
>
> On 7/25/05, sissonj@insession.com <si...@insession.com> wrote:
> > Davanum Srinivas <da...@gmail.com> wrote on 26/07/2005 09:22:34 AM:
> >
> > > Javamail & Axis...
> > >
> > > - Am done with changes to JavaMail. tests are working as well.
> >
> > Dims, are you going to build a new release candidate of the javamail
spec
> > jar - GERONIMO-802 and update the M4 branch to point to it?
>
> Could someone who has done it before do it please? I have no clue
> about the steps involved.
Ok, I'll do it tonight (Sydney time).
>
> > Currently both M4 and HEAD are using
> > geronimo_spec_javamail_version=1.3.1-rc4 which was built before some
of
> > you JavaMail spec changes.
> >
> > > - We most probably can't squeeze in a new release of Axis this week.
> > > What do we do? (dated snapshot?)
> >
> > Dated build sounds good to me. I don't think it should have SNAPSHOT
as
> > part of its version or name, as that would cause maven unnecessarily
check
> > for updates for it.
>
> Sounds good. Let me review the Axis bugs list and come up a dated
> build in the next few days.
>
> > Thanks,
> >
> > John
> > >
> > > thanks,
> > > -- dims
> > >
> > > On 7/25/05, David Blevins <da...@visi.com> wrote:
> > > > Alright, here is the deal on M4. We have OSCON coming up and from
my
> > > > experience, if we don't get M4 out the door this week, then we
won't
> > > > see it till the week after OSCON. I actually tried to cut M3 at
> > > > OSCON last year and we all know how that went.
> > > >
> > > > If we don't get M4 out the door this week, our hopes of having M5
by
> > > > the 15th are lost. Assuming we don't want this to happen, here is
my
> > > > attack plan:
> > > >
> > > > =ATTACK PLAN==========
> > > >
> > > > LAST ISSUES
> > > >
> > > > - Undeployment issue (GERONIMO-812, David Jencks)
> > > > - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> > > > ServiceMix=>Hiram, tmpOrb=>Dain)
> > > > - Web Services startup issue (GERONIMO-785, David Blevins)
> > > > - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> > > > - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> > > > - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> > > > completely)
> > > >
> > > > No sitting on tasks, if you are not going to do it, mark it
> > unassigned.
> > > >
> > > > Issue GERONIMO-811 is unassigned. Can someone either remove the
> > > > Tomcat option from the IzPack installer or add a the link to the
wiki?
> > > >
> > > > It seems GERONIMO-809 is actually completed, is that right?
> > > >
> > > > THE FINAL STUFF
> > > >
> > > > We have to run the TCK on the final binary, which means we need to
> > > > allow for a couple days of just testing the actual geronimo-1.0-
> > > > M4.zip that people will download. To even get that far, we need
to:
> > > >
> > > > 1. [notes] Create release notes for M4 and check them into the
QA
> > > > branch
> > > > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > > > 3. [dist] Cut and sign the binary and source distributions
> > > >
> > > > We are going to need to be done with the remaining JIRA items
above
> > > > by like Wednesday (best) or Thursday morning in order to do the
above
> > > > tasks.
> > > >
> > > > I am willing to take care of the svn and dist work. Side-note: I
have
> > > > to go to a wedding on Friday, so I personally would like to shoot
for
> > > > Wednesday as Thursday night is too late for me.
> > > >
> > > > Aaron, you willing to do the nice release notes like you did for
M3?
> > > >
> > > > ====================
> > > >
> > > > Sound good to everyone? Going to assume a lazy consensus
otherwise.
> > > >
> > > > -David
> > > >
> > > >
> > >
> > >
> > > --
> > > Davanum Srinivas -http://blogs.cocoondev.org/dims/
> >
> >
>
>
> --
> Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Attacking M4
Posted by Davanum Srinivas <da...@gmail.com>.
sisson,
On 7/25/05, sissonj@insession.com <si...@insession.com> wrote:
> Davanum Srinivas <da...@gmail.com> wrote on 26/07/2005 09:22:34 AM:
>
> > Javamail & Axis...
> >
> > - Am done with changes to JavaMail. tests are working as well.
>
> Dims, are you going to build a new release candidate of the javamail spec
> jar - GERONIMO-802 and update the M4 branch to point to it?
Could someone who has done it before do it please? I have no clue
about the steps involved.
> Currently both M4 and HEAD are using
> geronimo_spec_javamail_version=1.3.1-rc4 which was built before some of
> you JavaMail spec changes.
>
> > - We most probably can't squeeze in a new release of Axis this week.
> > What do we do? (dated snapshot?)
>
> Dated build sounds good to me. I don't think it should have SNAPSHOT as
> part of its version or name, as that would cause maven unnecessarily check
> for updates for it.
Sounds good. Let me review the Axis bugs list and come up a dated
build in the next few days.
> Thanks,
>
> John
> >
> > thanks,
> > -- dims
> >
> > On 7/25/05, David Blevins <da...@visi.com> wrote:
> > > Alright, here is the deal on M4. We have OSCON coming up and from my
> > > experience, if we don't get M4 out the door this week, then we won't
> > > see it till the week after OSCON. I actually tried to cut M3 at
> > > OSCON last year and we all know how that went.
> > >
> > > If we don't get M4 out the door this week, our hopes of having M5 by
> > > the 15th are lost. Assuming we don't want this to happen, here is my
> > > attack plan:
> > >
> > > =ATTACK PLAN==========
> > >
> > > LAST ISSUES
> > >
> > > - Undeployment issue (GERONIMO-812, David Jencks)
> > > - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> > > ServiceMix=>Hiram, tmpOrb=>Dain)
> > > - Web Services startup issue (GERONIMO-785, David Blevins)
> > > - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> > > - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> > > - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> > > completely)
> > >
> > > No sitting on tasks, if you are not going to do it, mark it
> unassigned.
> > >
> > > Issue GERONIMO-811 is unassigned. Can someone either remove the
> > > Tomcat option from the IzPack installer or add a the link to the wiki?
> > >
> > > It seems GERONIMO-809 is actually completed, is that right?
> > >
> > > THE FINAL STUFF
> > >
> > > We have to run the TCK on the final binary, which means we need to
> > > allow for a couple days of just testing the actual geronimo-1.0-
> > > M4.zip that people will download. To even get that far, we need to:
> > >
> > > 1. [notes] Create release notes for M4 and check them into the QA
> > > branch
> > > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > > 3. [dist] Cut and sign the binary and source distributions
> > >
> > > We are going to need to be done with the remaining JIRA items above
> > > by like Wednesday (best) or Thursday morning in order to do the above
> > > tasks.
> > >
> > > I am willing to take care of the svn and dist work. Side-note: I have
> > > to go to a wedding on Friday, so I personally would like to shoot for
> > > Wednesday as Thursday night is too late for me.
> > >
> > > Aaron, you willing to do the nice release notes like you did for M3?
> > >
> > > ====================
> > >
> > > Sound good to everyone? Going to assume a lazy consensus otherwise.
> > >
> > > -David
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas -http://blogs.cocoondev.org/dims/
>
>
--
Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Attacking M4
Posted by si...@insession.com.
Davanum Srinivas <da...@gmail.com> wrote on 26/07/2005 09:22:34 AM:
> Javamail & Axis...
>
> - Am done with changes to JavaMail. tests are working as well.
Dims, are you going to build a new release candidate of the javamail spec
jar - GERONIMO-802 and update the M4 branch to point to it?
Currently both M4 and HEAD are using
geronimo_spec_javamail_version=1.3.1-rc4 which was built before some of
you JavaMail spec changes.
> - We most probably can't squeeze in a new release of Axis this week.
> What do we do? (dated snapshot?)
Dated build sounds good to me. I don't think it should have SNAPSHOT as
part of its version or name, as that would cause maven unnecessarily check
for updates for it.
Thanks,
John
>
> thanks,
> -- dims
>
> On 7/25/05, David Blevins <da...@visi.com> wrote:
> > Alright, here is the deal on M4. We have OSCON coming up and from my
> > experience, if we don't get M4 out the door this week, then we won't
> > see it till the week after OSCON. I actually tried to cut M3 at
> > OSCON last year and we all know how that went.
> >
> > If we don't get M4 out the door this week, our hopes of having M5 by
> > the 15th are lost. Assuming we don't want this to happen, here is my
> > attack plan:
> >
> > =ATTACK PLAN==========
> >
> > LAST ISSUES
> >
> > - Undeployment issue (GERONIMO-812, David Jencks)
> > - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> > ServiceMix=>Hiram, tmpOrb=>Dain)
> > - Web Services startup issue (GERONIMO-785, David Blevins)
> > - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> > - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> > - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> > completely)
> >
> > No sitting on tasks, if you are not going to do it, mark it
unassigned.
> >
> > Issue GERONIMO-811 is unassigned. Can someone either remove the
> > Tomcat option from the IzPack installer or add a the link to the wiki?
> >
> > It seems GERONIMO-809 is actually completed, is that right?
> >
> > THE FINAL STUFF
> >
> > We have to run the TCK on the final binary, which means we need to
> > allow for a couple days of just testing the actual geronimo-1.0-
> > M4.zip that people will download. To even get that far, we need to:
> >
> > 1. [notes] Create release notes for M4 and check them into the QA
> > branch
> > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > 3. [dist] Cut and sign the binary and source distributions
> >
> > We are going to need to be done with the remaining JIRA items above
> > by like Wednesday (best) or Thursday morning in order to do the above
> > tasks.
> >
> > I am willing to take care of the svn and dist work. Side-note: I have
> > to go to a wedding on Friday, so I personally would like to shoot for
> > Wednesday as Thursday night is too late for me.
> >
> > Aaron, you willing to do the nice release notes like you did for M3?
> >
> > ====================
> >
> > Sound good to everyone? Going to assume a lazy consensus otherwise.
> >
> > -David
> >
> >
>
>
> --
> Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Attacking M4
Posted by Davanum Srinivas <da...@gmail.com>.
Javamail & Axis...
- Am done with changes to JavaMail. tests are working as well.
- We most probably can't squeeze in a new release of Axis this week.
What do we do? (dated snapshot?)
thanks,
-- dims
On 7/25/05, David Blevins <da...@visi.com> wrote:
> Alright, here is the deal on M4. We have OSCON coming up and from my
> experience, if we don't get M4 out the door this week, then we won't
> see it till the week after OSCON. I actually tried to cut M3 at
> OSCON last year and we all know how that went.
>
> If we don't get M4 out the door this week, our hopes of having M5 by
> the 15th are lost. Assuming we don't want this to happen, here is my
> attack plan:
>
> =ATTACK PLAN==========
>
> LAST ISSUES
>
> - Undeployment issue (GERONIMO-812, David Jencks)
> - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> ServiceMix=>Hiram, tmpOrb=>Dain)
> - Web Services startup issue (GERONIMO-785, David Blevins)
> - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
> - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> completely)
>
> No sitting on tasks, if you are not going to do it, mark it unassigned.
>
> Issue GERONIMO-811 is unassigned. Can someone either remove the
> Tomcat option from the IzPack installer or add a the link to the wiki?
>
> It seems GERONIMO-809 is actually completed, is that right?
>
> THE FINAL STUFF
>
> We have to run the TCK on the final binary, which means we need to
> allow for a couple days of just testing the actual geronimo-1.0-
> M4.zip that people will download. To even get that far, we need to:
>
> 1. [notes] Create release notes for M4 and check them into the QA
> branch
> 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> 3. [dist] Cut and sign the binary and source distributions
>
> We are going to need to be done with the remaining JIRA items above
> by like Wednesday (best) or Thursday morning in order to do the above
> tasks.
>
> I am willing to take care of the svn and dist work. Side-note: I have
> to go to a wedding on Friday, so I personally would like to shoot for
> Wednesday as Thursday night is too late for me.
>
> Aaron, you willing to do the nice release notes like you did for M3?
>
> ====================
>
> Sound good to everyone? Going to assume a lazy consensus otherwise.
>
> -David
>
>
--
Davanum Srinivas -http://blogs.cocoondev.org/dims/
Re: Attacking M4 - Final stuff
Posted by David Blevins <da...@visi.com>.
Ok, brand new binaries have ben published from the latest M4 tag:
http://cvs.apache.org/dist/geronimo/unstable/1.0-M4/
If there are no more negative ones and the binaries pass the TCK, we are good to go.
If you feel the urge to negative one something, please just fix it if you have the time.
-David
On Mon, Aug 01, 2005 at 02:36:48PM -0500, David Blevins wrote:
> Alright, we have closed all the JIRA issues and successfully ran all
> the TCK tests.
>
> Time for the "final stuff"
>
> On Mon, Jul 25, 2005 at 04:59:47PM -0500, David Blevins wrote:
> > THE FINAL STUFF
> >
> > We have to run the TCK on the final binary, which means we need to
> > allow for a couple days of just testing the actual geronimo-1.0-
> > M4.zip that people will download. To even get that far, we need to:
> >
> > 1. [notes] Create release notes for M4 and check them into the QA
> > branch
> > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > 3. [dist] Cut and sign the binary and source distributions
> >
>
> Aaron cleared up 1. I'm going to take care of 2 and 3. We should
> have binaries up shortly for voting and one final TCK sweep.
>
> -David
Re: Attacking M4 - Final stuff
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Just to clarify, the release notes I put out don't include the
last few days' worth of JIRA closures. We need to update them at least 1
more time before cutting the final packages. That doesn't need to hold up
any other testing, but I'd like to do it as close to the last minute as
possible.
Also, there was some uncertainty over whether to mention that
we'll provide our TCK plans to J2EE licensees who want to work with
Geronimo. I thought it would be cool to mention it as it might help drum
up some more vendor interest, and I don't feel like we should limit who we
offer it to to the 1 or 2 companies currently on the table. But I don't
feel super strongly if others have a good reason to withhold mention of
it (like, it may violate our own license agreement or something).
Aaron
On Mon, 1 Aug 2005, David Blevins wrote:
> Alright, we have closed all the JIRA issues and successfully ran all
> the TCK tests.
>
> Time for the "final stuff"
>
> On Mon, Jul 25, 2005 at 04:59:47PM -0500, David Blevins wrote:
> > THE FINAL STUFF
> >
> > We have to run the TCK on the final binary, which means we need to
> > allow for a couple days of just testing the actual geronimo-1.0-
> > M4.zip that people will download. To even get that far, we need to:
> >
> > 1. [notes] Create release notes for M4 and check them into the QA
> > branch
> > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > 3. [dist] Cut and sign the binary and source distributions
> >
>
> Aaron cleared up 1. I'm going to take care of 2 and 3. We should
> have binaries up shortly for voting and one final TCK sweep.
>
> -David
>
Re: Attacking M4 - Final stuff
Posted by David Blevins <da...@visi.com>.
On Mon, Aug 01, 2005 at 11:49:20PM -0700, David Jencks wrote:
> I see dblevins has posted source and binary tar.gzs etc but I have
> no idea how to produce them from a plain maven build. I consider
> his publish_build.sh script unacceptable for releases because it
> modifies what is checked out from svn.
I'm happy to create scripts so that people don't have to spend time
typing commands but am also very happy to see someone else implement
their ideal release proceedure in jelly or bash or java or anything
really.
As far as the script I've been using, I've created a new one and
removed tons of the parts that don't apply to official releases.
Again, if people are really unhappy with the scripts I've made for us
or they are unmaintainable or anything, I'm happy to remove them to
avoid the conflict.
> I'm going to start running tck tests on my build and hope we can
> straighten out how to package stuff up later. If there are problems
> tomorrow I can always start over.
IIRC, we need to run the tests on the binaries that we indent to ship.
-David
Re: Attacking M4 - Final stuff
Posted by David Jencks <da...@yahoo.com>.
On Aug 1, 2005, at 5:53 PM, Jeremy Boynes wrote:
> David Jencks wrote:
>> I rescusitated the M4 branch and removed the snapshot tag from the
>> deploy plugin and the numbered version from the packaging plugin.
>
> I think we should remove all SNAPSHOT references including those in
> the sandbox and in plugins we are not using. This can be done by
> fixing them to use the POM current version, or by removing those
> modules entirely (e.g. sandbox probably does not want to be in the
> release tag at all).
>
>> I think we should do a build from the branch, test it, and if it
>> works, then make the tag.
>
> Agreed. Let's clean up the cruft and reduce to the minimum number of
> version definitions (just etc/project.properties and project.xml for
> the plugins?). We can do a build there using an explicit revision
> number, then if we are happy copy that rev to the tag.
I've removed all the 'SNAPSHOT' and other hard coded versions I can
find and successfully built geronimo from rev 226951 after removing my
maven geronimo and geronimo-spec repository entries. I see dblevins
has posted source and binary tar.gzs etc but I have no idea how to
produce them from a plain maven build. I consider his publish_build.sh
script unacceptable for releases because it modifies what is checked
out from svn.
I'm going to start running tck tests on my build and hope we can
straighten out how to package stuff up later. If there are problems
tomorrow I can always start over.
thanks
david jencks
>
>> IIUC aaron is fixing the release notes so I hope we can get them
>> finalized by tonight also.
>
> Lets be careful this time and make sure everything is in order first.
> --
> Jeremy
>
Re: Attacking M4 - Final stuff
Posted by Jeremy Boynes <jb...@apache.org>.
David Jencks wrote:
> I rescusitated the M4 branch and removed the snapshot tag from the
> deploy plugin and the numbered version from the packaging plugin.
>
I think we should remove all SNAPSHOT references including those in the
sandbox and in plugins we are not using. This can be done by fixing them
to use the POM current version, or by removing those modules entirely
(e.g. sandbox probably does not want to be in the release tag at all).
> I think we should do a build from the branch, test it, and if it works,
> then make the tag.
>
Agreed. Let's clean up the cruft and reduce to the minimum number of
version definitions (just etc/project.properties and project.xml for the
plugins?). We can do a build there using an explicit revision number,
then if we are happy copy that rev to the tag.
> IIUC aaron is fixing the release notes so I hope we can get them
> finalized by tonight also.
>
Lets be careful this time and make sure everything is in order first.
--
Jeremy
Re: Attacking M4 - Final stuff
Posted by David Jencks <dj...@gluecode.com>.
I rescusitated the M4 branch and removed the snapshot tag from the
deploy plugin and the numbered version from the packaging plugin.
I think we should do a build from the branch, test it, and if it works,
then make the tag.
IIUC aaron is fixing the release notes so I hope we can get them
finalized by tonight also.
thanks
david jencks
On Aug 1, 2005, at 4:13 PM, David Jencks wrote:
> It's a big nuisance, but I agree with Jeremy that we need to rebuild
> with the SNAPSHOT tags removed. We also need a little better
> coordination and better release procedures :-)
>
> thanks
> david jencks
>
> On Aug 1, 2005, at 3:52 PM, Jeremy Boynes wrote:
>
>> Aaron Mulder wrote:
>>> I just mentioned this, but... the release notes MUST be updated
>>> again before the final binary is posted. If nothing else, they say
>>> "NOT FINAL RELEASE NOTES" in the first 2 lines. :) I'll try to do
>>> it this afternoon.
>>> Thanks,
>>> Aaron
>>> P.S. When I do an "svn up" on the v1_0_M4-QA branch right now, I get:
>>> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
>>> svn:
>>> Cannot replace a directory from within
>>
>> I would guess that David "svn move"d the branch to the tag rather
>> than copying it. You should copy back in the one from before he
>> bumped the version number.
>>
>> --
>> Jeremy
>>
>
Re: Attacking M4 - Final stuff
Posted by David Jencks <dj...@gluecode.com>.
It's a big nuisance, but I agree with Jeremy that we need to rebuild
with the SNAPSHOT tags removed. We also need a little better
coordination and better release procedures :-)
thanks
david jencks
On Aug 1, 2005, at 3:52 PM, Jeremy Boynes wrote:
> Aaron Mulder wrote:
>> I just mentioned this, but... the release notes MUST be updated
>> again before the final binary is posted. If nothing else, they say
>> "NOT FINAL RELEASE NOTES" in the first 2 lines. :) I'll try to do
>> it this afternoon.
>> Thanks,
>> Aaron
>> P.S. When I do an "svn up" on the v1_0_M4-QA branch right now, I get:
>> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
>> svn:
>> Cannot replace a directory from within
>
> I would guess that David "svn move"d the branch to the tag rather than
> copying it. You should copy back in the one from before he bumped the
> version number.
>
> --
> Jeremy
>
Re: Attacking M4 - Final stuff
Posted by Jeremy Boynes <jb...@apache.org>.
Aaron Mulder wrote:
> I just mentioned this, but... the release notes MUST be updated
> again before the final binary is posted. If nothing else, they say "NOT
> FINAL RELEASE NOTES" in the first 2 lines. :) I'll try to do it this
> afternoon.
>
> Thanks,
> Aaron
>
> P.S. When I do an "svn up" on the v1_0_M4-QA branch right now, I get:
>
> svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
> svn:
> Cannot replace a directory from within
>
I would guess that David "svn move"d the branch to the tag rather than
copying it. You should copy back in the one from before he bumped the
version number.
--
Jeremy
Re: Attacking M4 - Final stuff
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
I just mentioned this, but... the release notes MUST be updated
again before the final binary is posted. If nothing else, they say "NOT
FINAL RELEASE NOTES" in the first 2 lines. :) I'll try to do it this
afternoon.
Thanks,
Aaron
P.S. When I do an "svn up" on the v1_0_M4-QA branch right now, I get:
svn: REPORT request failed on '/repos/asf/!svn/vcc/default'
svn:
Cannot replace a directory from within
On Mon, 1 Aug 2005, David Blevins wrote:
> Ok. The binaries are now uploading to :
>
> http://cvs.apache.org/dist/geronimo/unstable/1.0-M4/
>
> If this passes the TCK and we vote to accept it , we can just copy that directory to where the other milestones are.
>
> -David
>
Re: Attacking M4 - Final stuff
Posted by Jeremy Boynes <jb...@apache.org>.
David Blevins wrote:
>
>
> Ok. The binaries are now uploading to :
>
> http://cvs.apache.org/dist/geronimo/unstable/1.0-M4/
>
> If this passes the TCK and we vote to accept it , we can just copy
> that directory to where the other milestones are.
>
This is based on a bad tag and should be removed.
--
Jeremy
Re: Attacking M4 - Final stuff
Posted by David Blevins <da...@visi.com>.
On Mon, Aug 01, 2005 at 02:36:48PM -0500, David Blevins wrote:
> Alright, we have closed all the JIRA issues and successfully ran all
> the TCK tests.
>
> Time for the "final stuff"
>
> On Mon, Jul 25, 2005 at 04:59:47PM -0500, David Blevins wrote:
> > THE FINAL STUFF
> >
> > We have to run the TCK on the final binary, which means we need to
> > allow for a couple days of just testing the actual geronimo-1.0-
> > M4.zip that people will download. To even get that far, we need to:
> >
> > 1. [notes] Create release notes for M4 and check them into the QA
> > branch
> > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > 3. [dist] Cut and sign the binary and source distributions
> >
>
> Aaron cleared up 1. I'm going to take care of 2 and 3. We should
> have binaries up shortly for voting and one final TCK sweep.
>
Ok. The binaries are now uploading to :
http://cvs.apache.org/dist/geronimo/unstable/1.0-M4/
If this passes the TCK and we vote to accept it , we can just copy that directory to where the other milestones are.
-David
Re: Attacking M4 - Final stuff
Posted by David Blevins <da...@visi.com>.
Alright, we have closed all the JIRA issues and successfully ran all
the TCK tests.
Time for the "final stuff"
On Mon, Jul 25, 2005 at 04:59:47PM -0500, David Blevins wrote:
> THE FINAL STUFF
>
> We have to run the TCK on the final binary, which means we need to
> allow for a couple days of just testing the actual geronimo-1.0-
> M4.zip that people will download. To even get that far, we need to:
>
> 1. [notes] Create release notes for M4 and check them into the QA
> branch
> 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> 3. [dist] Cut and sign the binary and source distributions
>
Aaron cleared up 1. I'm going to take care of 2 and 3. We should
have binaries up shortly for voting and one final TCK sweep.
-David
RE: Attacking M4
Posted by Jeff Genender <jg...@savoirtech.com>.
> -----Original Message-----
> From: sissonj@insession.com [mailto:sissonj@insession.com]
> Sent: Monday, July 25, 2005 6:01 PM
> To: dev@geronimo.apache.org
> Subject: Re: Attacking M4
>
> David Blevins <da...@visi.com> wrote on 26/07/2005
> 07:59:47 AM:
>
> > Alright, here is the deal on M4. We have OSCON coming up
> and from my
> > experience, if we don't get M4 out the door this week, then
> we won't
> > see it till the week after OSCON. I actually tried to cut
> M3 at OSCON
> > last year and we all know how that went.
> >
> > If we don't get M4 out the door this week, our hopes of
> having M5 by
> > the 15th are lost. Assuming we don't want this to happen,
> here is my
> > attack plan:
> >
> > =ATTACK PLAN==========
> >
> > LAST ISSUES
> >
> > - Undeployment issue (GERONIMO-812, David Jencks)
> > - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> > ServiceMix=>Hiram, tmpOrb=>Dain)
> > - Web Services startup issue (GERONIMO-785, David Blevins)
> > - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> > - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
>
> See comments below.
>
> > - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> > completely)
> >
> > No sitting on tasks, if you are not going to do it, mark it
> unassigned.
> >
> > Issue GERONIMO-811 is unassigned. Can someone either remove the
> > Tomcat option from the IzPack installer or add a the link
> to the wiki?
>
> Jeff, any comment here? I can modify the installer to not
> have the Tomcat option for M4. I now feel we are better
> waiting and providing the Tomcat functionality in an unstable
> build from HEAD or M5, working on making it as simple as
> possible for the user to configure and provide good
> documentation with the installation.
M5 is better IMHO.
>
> I tried using M4 with Jetty disabled last night and had some
> problems (ran out of time to debug.. was getting late). It
> may be something I did wrong, see mail thread "Problems
> running DebugConsole on Tomcat, with Jetty removed from plans in M4".
Probably a small issue with the plans...I could look into it. If we are
talking about a mid/end-August M5, we could wait. If you want the final
Tomcat plans for M4, I could get that for you as well. What do you think?
>
> John
>
> >
> > It seems GERONIMO-809 is actually completed, is that right?
>
> GERONIMO-809 is complete now. JIRA being down prevented me
> from completing it last night.
>
>
> >
> > THE FINAL STUFF
> >
> > We have to run the TCK on the final binary, which means we need to
> > allow for a couple days of just testing the actual geronimo-1.0-
> > M4.zip that people will download. To even get that far, we need to:
> >
> > 1. [notes] Create release notes for M4 and check them
> into the QA
> > branch
> > 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> > 3. [dist] Cut and sign the binary and source distributions
> >
> > We are going to need to be done with the remaining JIRA items above
> > by like Wednesday (best) or Thursday morning in order to do
> the above
> > tasks.
> >
> > I am willing to take care of the svn and dist work.
> Side-note: I have
> > to go to a wedding on Friday, so I personally would like to
> shoot for
> > Wednesday as Thursday night is too late for me.
> >
> > Aaron, you willing to do the nice release notes like you did for M3?
> >
> > ====================
> >
> > Sound good to everyone? Going to assume a lazy consensus otherwise.
> >
> > -David
> >
>
> This e-mail message and any attachments may contain confidential,
> proprietary or non-public information. This information is intended
> solely for the designated recipient(s). If an addressing or
> transmission
> error has misdirected this e-mail, please notify the sender
> immediately
> and destroy this e-mail. Any review, dissemination, use or
> reliance upon
> this information by unintended recipients is prohibited. Any
> opinions
> expressed in this e-mail are those of the author personally.
>
Re: Attacking M4
Posted by si...@insession.com.
David Blevins <da...@visi.com> wrote on 26/07/2005 07:59:47 AM:
> Alright, here is the deal on M4. We have OSCON coming up and from my
> experience, if we don't get M4 out the door this week, then we won't
> see it till the week after OSCON. I actually tried to cut M3 at
> OSCON last year and we all know how that went.
>
> If we don't get M4 out the door this week, our hopes of having M5 by
> the 15th are lost. Assuming we don't want this to happen, here is my
> attack plan:
>
> =ATTACK PLAN==========
>
> LAST ISSUES
>
> - Undeployment issue (GERONIMO-812, David Jencks)
> - Snapshots (Javamail & Axis=>Dims, jUDDI & Scout=>Geir,
> ServiceMix=>Hiram, tmpOrb=>Dain)
> - Web Services startup issue (GERONIMO-785, David Blevins)
> - Corba interop problem (GERONIMO-813, Dain Sundstrom)
> - Izpack/Tomcat issue (GERONIMO-811, Unassigned)
See comments below.
> - Unknown CTS issues (need to clear up GERONIMO-812 to run it
> completely)
>
> No sitting on tasks, if you are not going to do it, mark it unassigned.
>
> Issue GERONIMO-811 is unassigned. Can someone either remove the
> Tomcat option from the IzPack installer or add a the link to the wiki?
Jeff, any comment here? I can modify the installer to not have the Tomcat
option for M4. I now feel we are better waiting and providing the Tomcat
functionality in an unstable build from HEAD or M5, working on making it
as simple as possible for the user to configure and provide good
documentation with the installation.
I tried using M4 with Jetty disabled last night and had some problems (ran
out of time to debug.. was getting late). It may be something I did
wrong, see mail thread "Problems running DebugConsole on Tomcat, with
Jetty removed from plans in M4".
John
>
> It seems GERONIMO-809 is actually completed, is that right?
GERONIMO-809 is complete now. JIRA being down prevented me from
completing it last night.
>
> THE FINAL STUFF
>
> We have to run the TCK on the final binary, which means we need to
> allow for a couple days of just testing the actual geronimo-1.0-
> M4.zip that people will download. To even get that far, we need to:
>
> 1. [notes] Create release notes for M4 and check them into the QA
> branch
> 2. [svn] Close the QA branch and copy it to tags/v1_0_M4
> 3. [dist] Cut and sign the binary and source distributions
>
> We are going to need to be done with the remaining JIRA items above
> by like Wednesday (best) or Thursday morning in order to do the above
> tasks.
>
> I am willing to take care of the svn and dist work. Side-note: I have
> to go to a wedding on Friday, so I personally would like to shoot for
> Wednesday as Thursday night is too late for me.
>
> Aaron, you willing to do the nice release notes like you did for M3?
>
> ====================
>
> Sound good to everyone? Going to assume a lazy consensus otherwise.
>
> -David
>
This e-mail message and any attachments may contain confidential,
proprietary or non-public information. This information is intended
solely for the designated recipient(s). If an addressing or transmission
error has misdirected this e-mail, please notify the sender immediately
and destroy this e-mail. Any review, dissemination, use or reliance upon
this information by unintended recipients is prohibited. Any opinions
expressed in this e-mail are those of the author personally.